[xsd-users] customising XSD to use ICU

[Bradley Beddoes]

So I got a fair way with all of this, I had the UnicodeString integrated 
for most things but there were a number of problems:

- Firstly you need to write a lot of specific cases for your string 
class constructor, this is expected but be warned :).

- Comparison for things like enum seem to have const char* [*i] != *this 
generated so writing an overloaded != operator in my new string class 
was impossible (of course I did make this work by manually editing the 
positions, might be worth changing in the generation logic not sure).

- Exceptions. Most exception classes are hard wired to take 
basic_string<C>, in some cases multiple basic_strings, would be a lot of 
overhead to replace this and for some reasons I ran into problems when 
attempting to.

- Numero Uno problem... serialization, this I just cannot solve, I get 
so many errors when attempting to compile generated code with 
serialization enabled that I have little to no idea where to start, 
given timelines and the fact I need to have serialization work properly 
this seems a show stopper.

So I will revert back to using wchar_t my 2 days experiment didn't come 
to much fruition but thems the breaks, should anyone else ever pick this 
up in the future and are more successful then me drop me a note!.

I may look at some way of writing a thin wrapper or something for ICU if 
I have any outcomes in that dept I will report back.

cheers,
Bradley

-- 
Bradley Beddoes
Lead Software Architect

Intient - "Open Source, Open Standards"