Re: [Corelinux-develop] Thought, parser, template

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

Hans - Dulimarta wrote:
> 
> On Sat, 24 Feb 2001, Frank V. Castellucci wrote:
> 
> > Hans - Dulimarta wrote:
> > >
> > > On Fri, 23 Feb 2001, Frank V. Castellucci wrote:
> > >
> > > > Hans,
> > > >
> > > > As per previous conversation (corelinux, clfw, clfll), did you see
> > > > anything of interest? Is there something you want to do that isn't on
> > > > the list that makes sense for the direction of the libraries?
> > > >
> > >
> > > My exploration in corelinux in not yet comprehensive. It is a new world to
> > > me, let alone the framework (clfw) and the library loader (clfll). All
> > > these three tracks are interesting to me, but I'll continue my exploration
> > > in the corelinux world first.
> > >
> > > In the task list I found that #11180 and #11325 are unassigned.
> > > I'll take care of #11325 first, it has been past due for > 1 year :-)
> >
> > Which one is 11325 again? I can't seem to get it on the web.
> >
> 
> Task ID 11325: libcl++ implementation of Factory Method Pattern (Req 5097)

hmmmm, that has been implemented as AbstractAllocator in AbstractFactory
<grin>.
You may want to review it as I may have not done a good job on it,
but...

> 
> > Couple of things:
> >
> > A templated declaration is useless until it has it's types defined, only
> > then is it a concrete class/object. The only way I have ever gotten
> > templated classes to work with generating their own meta-information was
> > to first create the concrete entity, and then the macro.
> >
> > The whole idea of what Christophe is doing would be to do away with the
> > meta-macros, and instead use a more expressive and easy to read form for
> > which we generate the needed constructs. If you think about it, the
> > metatype/metaclass itself is mostly a collection of dictionaries
> > (relationships, data-members, methods, etc.).
> >
> > The road into #define SOME_MACRO1() .... SOME_MACRO[n]() is exactley
> > what I avoided with the way I constructed the first round, NO LIMITS!!!
> > But, as you can see, it means more work on the developers part.
> >
> 
> With this parser work on the way, are we going to adapt a similar
> approach to that of Qt with their 'Meta Object Compiler' (moc)?

I imagine so if Qt was going for the same idea. I haven't developed with
Qt. 

> Perhaps I missed something here because during the initial traffic of
> MetaClass discussion sometimes back last year, my focus was somewhere
> else.

I don't know, you seem in tune. I think I have more in my mind about
MetaClass, Meta Object Protocols, Reflection, and Introspection then I
may have indicated in these posts, but we can evolve that.


> 
> > > --
> > > Hans Dulimarta, Ph.D. |                dul...@co...
> > > Research Associate    |     http://www.egr.msu.edu/~dulimart
> > > P: 517-432-7589       |     http://corelinux.sourceforge.net
> > > F: 760-281-7691     http://freshmeat.net/projects/snapsource
> > > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> > >
> > > _______________________________________________
> > > Corelinux-develop mailing list
> > > Cor...@li...
> > > http://lists.sourceforge.net/lists/listinfo/corelinux-develop
> >
> >
> 
> --
> Hans Dulimarta, Ph.D. |                dul...@co...
> Research Associate    |     http://www.egr.msu.edu/~dulimart
> P: 517-432-7589       |     http://corelinux.sourceforge.net
> F: 760-281-7691     http://freshmeat.net/projects/snapsource
> Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> 
> _______________________________________________
> 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