From: Neulinger, N. <nn...@um...> - 2006-03-22 13:36:22
|
I'm fine with adding those so they are not external dependencies... Did you have specific uses in mind? -- Nathan =20 ------------------------------------------------------------ Nathan Neulinger EMail: nn...@um... University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 =20 > -----Original Message----- > From: tor...@li...=20 > [mailto:tor...@li...] On Behalf=20 > Of Thomas Porschberg > Sent: Wednesday, March 22, 2006 1:07 AM > To: tor...@li... > Subject: [Tora-develop] proposal for two new external libs >=20 > Hi, >=20 > I would like to suggest the integration of two more external=20 > libraries=20 > to TOra. Two more libs means usually two more dependencies=20 > which is not > desirable. I will explain why it would not be so critical in=20 > the case I > suggest. >=20 > first library: Loki > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > location: http://sourceforge.net/projects/loki-lib/ > license: MIT license -> http://en.wikipedia.org/wiki/MIT_license > purpose: from the SF-page -> > A C++ library of designs, containing flexible implementations > of common design patterns and idioms. >=20 > The library is virtually complete implemented as template library. > For TOra it would be sufficient to plugin the loki-header files to > <project-root>/ext/loki and you are ready to use the library. >=20 > second library: CppUnit > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > location: http://cppunit.sourceforge.net/cppunit-wiki/FrontPage > license: GPL > purpose: C++ unit testing framework >=20 > CppUnit is not a pure template library so you need to link against it. > However things are not so bad because: >=20 > 1) linking against the lib is only neccessary for developers who want > to run a test, Users of TOra don't need the library. >=20 > 2) we would separate the tests from the sources, one additional > test directory under <project-root> >=20 > 3) library is available for *n*x and windows >=20 > 4) good support by autotools, you can run your tests by > calling "make check" >=20 > Cheers, > Thomas >=20 > --=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking=20 > scripting language > that extends applications into web and mobile media. Attend=20 > the live webcast > and join the prime developer group breaking into this new=20 > coding territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720& > dat=3D121642 > _______________________________________________ > Tora-develop mailing list > Tor...@li... > https://lists.sourceforge.net/lists/listinfo/tora-develop >=20 >=20 |
From: Thomas P. <th...@ra...> - 2006-03-22 20:55:10
|
Am Wed, 22 Mar 2006 07:36:05 -0600 schrieb "Neulinger, Nathan" <nn...@um...>: > I'm fine with adding those so they are not external dependencies... >=20 > Did you have specific uses in mind? >=20 Hi Nathan, I think both libraries are general purpose tools and useful for any TOra coding. Francesco already mentioned tosqlparse.cpp. I also think the class design of TOra has room for improvements and I think to be extensible and maintainable for the future some refactoring is not bad. Loki make some tasks like "making singleton classes" or "create an object factory" easy and could be of help by doing such refactoring. E.g. I extracted a small class toConfiguration from toTool which only has the responsibility to manage the Configuration map and I implemented the class as Singleton with Loki. BTW, I observed that in some h-files multiple class-interfaces are included. Let say I have foo.h and in foo.h I specify interfaces for classes A,B,C. Now another class D must include the interface of class B for some reason. I must therefore do a #include "foo.h". But now D depends on the interfaces of class A and C too, which is bad. When I now change interface of class A I have to recompile D :-(. I also observed some simply superfluous includes in header files. This leads to unneccessary compile dependencies too. I think it would be better to split foo.h in three different header files which can be separately included. The price are some more files but they are smaller and classes are not longer coupled tight together. As you can see, I hope both libs can help to make TOra better in small steps. Thomas > -- Nathan > =20 > ------------------------------------------------------------ > Nathan Neulinger EMail: nn...@um... > University of Missouri - Rolla Phone: (573) 341-6679 > UMR Information Technology Fax: (573) 341-4216 > =20 >=20 > > -----Original Message----- > > From: tor...@li...=20 > > [mailto:tor...@li...] On Behalf=20 > > Of Thomas Porschberg > > Sent: Wednesday, March 22, 2006 1:07 AM > > To: tor...@li... > > Subject: [Tora-develop] proposal for two new external libs > >=20 > > Hi, > >=20 > > I would like to suggest the integration of two more external=20 > > libraries=20 > > to TOra. Two more libs means usually two more dependencies=20 > > which is not > > desirable. I will explain why it would not be so critical in=20 > > the case I > > suggest. > >=20 > > first library: Loki > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 > > location: http://sourceforge.net/projects/loki-lib/ > > license: MIT license -> http://en.wikipedia.org/wiki/MIT_license > > purpose: from the SF-page -> > > A C++ library of designs, containing flexible > > implementations of common design patterns and idioms. > >=20 > > The library is virtually complete implemented as template library. > > For TOra it would be sufficient to plugin the loki-header files to > > <project-root>/ext/loki and you are ready to use the library. > >=20 > > second library: CppUnit > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 > > location: http://cppunit.sourceforge.net/cppunit-wiki/FrontPage > > license: GPL > > purpose: C++ unit testing framework > >=20 > > CppUnit is not a pure template library so you need to link against > > it. However things are not so bad because: > >=20 > > 1) linking against the lib is only neccessary for developers who > > want to run a test, Users of TOra don't need the library. > >=20 > > 2) we would separate the tests from the sources, one additional > > test directory under <project-root> > >=20 > > 3) library is available for *n*x and windows > >=20 > > 4) good support by autotools, you can run your tests by > > calling "make check" > >=20 > > Cheers, > > Thomas > >=20 > > --=20 > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking=20 > > scripting language > > that extends applications into web and mobile media. Attend=20 > > the live webcast > > and join the prime developer group breaking into this new=20 > > coding territory! > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720& > > dat=3D121642 > > _______________________________________________ > > Tora-develop mailing list > > Tor...@li... > > https://lists.sourceforge.net/lists/listinfo/tora-develop > >=20 > >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend > the live webcast and join the prime developer group breaking into > this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ Tora-develop mailing > list Tor...@li... > https://lists.sourceforge.net/lists/listinfo/tora-develop --=20 NO ePatents: http://swpat.ffii.org/index.de.html |