I am starting to doubt the header only principle of the netlib. If this is open for debate, than I think we should look at the time incurred not only by the compile length of the library, but also of recently employed dependencies (a spirit based URI implementation). It could be reasoned, if the time required for the tests is any indication, that they will only get longer for the end-user as features are added. At what point does this become intolerable? This library has barely scratched the surface, and it seems to me that it would behoove both the user and the developer if these times could be cut down.
John ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
