Re: [Corelinux-public] String Analysis, Design, Implementation open

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

Joe Nelson wrote:
> 
> > Unlike the patterns I have been working on, this one has some work to
> > do. Even if no one wants to grab the Analysis bull by the horns, we
> > should at least be discussing aspects of this like the detailed use
> > cases, like the std::basic_string interface where the type can be
> > ignored. I think this is a good chance to flex some of MagicDraw UML as
> > well once we enumerate the use cases.
> 
> How about making all strings be unicode?
> 

My mail keeps getting whacked. 

Joe,

If we just use Unicode then we either have to use another library, or
create one. What we originally proposed was to abstract the interface
and then provide some means to let users (developers) adapt another
string implementation to our interface. This is more complex but allows 

1. For CoreLinux++ we can implement classes that use the String
abstraction. This way we are confident (as much as can be) that the
developers choice of string implementation won't break us (see Adapter).

2. String implementations that haven't been developed yet to be use
later on (ditto Adapter).

3. Dynamic string changes in some cases (see Bridge).

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://www.colconsulting.com 
Object Oriented Analysis and Design |Java and C++ Development