|
From: Frank V. C. <fr...@co...> - 2001-02-06 17:33:45
|
Christophe, You are right. I had the namespace removed from the macro declaration (and instead opted for specific namespace qualifiers) because of a problem when you write and application around it (see the example exfl1) The fact that the definitions are in macros is hard to debug, but my thoughts were that they would just be used by the the types we define. For external users (developers/applications), I was going to expand the interface on MetaType and MetaClass so that they can be constructed at run time by applications that want to extend the ontologies. Thoughts? Christophe Prud'homme wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hie > > I used the metaclass/type framework and I must say that I went in lots of > trouble. > - - lots of compilation error if you do not use > using namespace corelinux > - - even with that there are some problems because not everything is in the > corelinux namespace > - - the fact that everything is pretty macro centric is REALLY hard to debug. > - - documentation is missing for explanation but I plan to write that. > > I have done some modifications in order to correct these problems (namespace > ones mainly) but some cleanup is needed first. > > best regards > C. > - -- > Christophe Prud'homme > OOA and OOD for Linux > CoreLinux -- http://corelinux.sourceforge.net > Finite Element Method Codes > KFem -- http://kfem.sourceforge.net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjqAFMwACgkQoY+0C9S+FFAaswCeNb+UkTaP7RZZ3cK2DGZzfjEU > QjYAoIV0e7qJBIQbLKNNzN+8vwd38ZmC > =zC+U > -----END PGP SIGNATURE----- > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/lists/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 |