Re: [Corelinux-develop] MetaClass parser

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> > Methinks that before you attempt writing anything we should discuss the
> > pitfalls and perils with such tools.
> I am open to discussion.
> The problem I see is to build a generic parser that could be extended in some
> sense by the user/programmer.
> In order to understand correctly the meta object concept I wrote my own meta
> object system. it is designed for a certain domain and it contains the same
> kind of features as your design.
> the parser in this case is not that difficult to implement.
> in the corelinux case, it is another story but worth the thinking.

The parser abstraction is not where I see problems, it is the
metatype/metaclass aspect especially one of synchronization. Once you
generate something, and it is edited, how do you preserve it.

> >
> > If you feel comfortable after that, I have some requirement/ideas I
> > would like to brush past you.
> what are they ?

Now that I see you are open to the converstation, I will gather my
thoughts and present a bigger document here to start with. In the
meantime, you may want to consider RDF as a syntax for the type
definitions.

> 
> 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
> 
> iEYEARECAAYFAjqVfLAACgkQoY+0C9S+FFB0YwCePLtTy5wKII+X05t9a6klHWIx
> +M0AnjGagnPgAVX1AbqyYW3K1nA/KON0
> =7ILH
> -----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