Re: [Corelinux-public] a few questions

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

James Sasitorn wrote:
> 
> Well, I have a few questions, so I'll just enumerate them. Most of which are
> nitpicky, but I'm curious...
> 
> 2. Is corelinux based on templates?

CoreLinux++ is based on good requirement review, good analysis, and good
detailed design, prior to implementation. If the analysis or design
shows that templates are a more qualified approach to a paricular
problem domain then we will use templates.

> I read the blurb on the use of templates. Static type checking is a really
> nice feature to have. Yet, if you look at a language like java, where all
> classes inherit from a superclass Object, non static type checking has its
> benefits.. Ie. the ability to stick almost anything in a hashtable. I see
> how this could be resolved using templates and a strict java-like class
> heirarchy..

I agree that there are times when a pervasive base object has
advantages. The Bridge Pattern uses this. CoreLinux++ is also strongly
supporting the STL standard. So as of now CoreLinux++ has a
CoreLinuxObject base class BUT it is not the base of all objects at this
point.
 
> 3. If you have a subclass specifically for UTF8, are you considering a
> subclass for each of the different regional encodings (theoretically, of
> course)?

This is a good point. Please keep in mind that the StringUtf8 that is in
the current code point is NOT, NOT, NOT what we want as a string. The
requirement is open and I wouldn't mind discussing it in the short term
to get it moving along.

> 4. Have you considered standarizing the types in an abstract header file.
> Similiar to what glib does...
> http://developer.gnome.org/doc/API/glib/glib-basic-types.html

See Types.hpp

> 
> 5. I noticed the use of doc++. Does documentation include the use of the
>     @param, @exception, features?

Yes.

> 6. What is the current stage of development?
> 
> thanks,
> 
> james

Well, the Analysis for the Structural Patterns has just been put up. I
also managed to get the initial design and implementation in for the
Adapter Pattern.

I am putting the final touches on the process to include From Design to
Implementation.

Requirements are still arriving, and anyone who wants to tackle the
process needs to own the requirement to implementation. But at this
point, no one has grabbed any except myself (I hope it is because of the
holidays, but some people e-mailed me that the process was to involved).

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux