|
From: Thomas M. <tma...@ze...> - 2000-10-23 18:58:06
|
"Frank V. Castellucci" wrote: > 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. Great, now I have to quit complaining :) So my question then is why Core*Linux*? Is this merely a dependency/complexity management issue? That is a very good issue. I guess I could start working on CoreWindows++ and CoreHPUX++, or maybe CoreLinux++*3, if I wanted to use it. -- Thomas O Matelich Senior Software Designer Zetec, Inc. sos...@us... tma...@ze... |