|
From: Frank V. C. <fr...@co...> - 2000-10-23 15:29:24
|
Thomas Matelich wrote: > "Frank V. Castellucci" wrote: > > > My post of asking Tom what "scared" him about the framework design > > something I thought he saw in the framework. While we are all concerned > > with providing libraries that are "useable", I have had no compunction > > about adding something complex to enhance the solution space options. > > This may be my background of big systems work, where lots of things are > > thought about. The biggest difference between SOMELib and CoreLinux++ is > > that your library addresses a specific need (and will do it well it > > appears), while CoreLinux++ is after a broad range of uses. > > My biggest problem with projects like CoreLinux++ is when they become all or > nothing. While it is a pain to rely on 12 different projects, being able to pick > your functionality from the best place is great. If the library loader relies on > the persistence framework which relies on the property accessing methods which > rely on the enhanced RTTI methodology, that is when I say nevermind. If this is > not true in CoreLinux++, hooray. Just my opinion. > Well said and I agree, and you can say hooray! More clarification: CoreLinux++ is not A framework, but many. It is not our intent to tightly couple each framework to each other, our disciplines will ensure that. In the event it is natural, for say the Persistence framework to use some kind of library loading capability, then we of course we use the abstraction of the Library Load framework. But it would be up to the solution space to instantiate the appropriate derivation. By the same token, our frameworks are to be "plug-in-able", if the user selects a persistence framework implementation that doesn't require other frameworks, that is fine as well. > > -- > Thomas O Matelich > Senior Software Designer > Zetec, Inc. > sos...@us... > tma...@ze... > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |