|
From: Frank V. C. <fr...@co...> - 2000-08-21 21:53:39
|
Christophe Prud'homme wrote: > > > the clfw should really be limited to abstract framework bases. In > > otherwords, the FunctionLibrary loader implementation is a separate > > deliverable that requires libclfrmwrk and libcorelinux. > > > > That way the user has the ability, in the long term, in substituting > > which FunctionLibrary framework that they want to use. Or they can > > create their own. > > > > I didn't want to force frameworks down anyones throat and this seemed > > the most flexible. Thoughts? > so you want to move it again ? No, I don't want to move clfw or any of the abstractions (Library Load, Persist, etc.) that will go with it. When I create the FunctionLibraryLoad implementation, though, it should be as separate as clfw is to corelinux. > provide it as an example ? > > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | Un prud'homme était un homme > Cambridge MA 02139 | d'honneur et de valeur, > Tel (Office) : (00 1) (617) 253 0229 | sage et loyal. > Fax (Office) : (00 1) (617) 258 8559 | -- Chateaubriand > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |