I've updated the class diagram again. This is a 'char as Option name'
free
zone ;) This results in a much cleaner API and a much nicer class
hierarchy. I would be in favour of this approach. It would of course
involve the user having to change the code.
I am going to implement an XML->Java co
I have done some more work on the class diagram
( http://www.integralsource.com/cli/datatype2.gif ). As you can see by
supporting the choice of 'char' and 'String' as the Option name the
design is much more complex. Wouldn't it be much better to drop
support for 'char'? This would simplify the d
