> AAN> Everybody get what they wnat, and we all lived happily ever
> AAN> after.
>
> Unless implemented in a manner that gives maintence problems...
?
Can you elaborate on that?
I think we would end up with something that is easier to maintain,
especially if we create an Encoding subdirectory for all the encoding
classes. We only need to export "Encoding.h" (and later "Unicode.h") to
the world. The rest are internal.
Now have a look at Encoding.h, and see how small it is.
That should prove to you that this scheme is nice and clean, and that the
interface is minimal. ;-)
Now have a look at the TextFormatter.C file. This one makes use of the
new scheme. There is *one* call regarding encodings in there. With this
one call, we get the encoding-independent property, i.e. support for all
encodings that we implement.
I don't see how this will give us maintainance problems...
Greets,
Asger
