>>>>> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> So, what magic should we add in there, besides defining a proper
>> wstring based on LString?
Asger> Nothing.
Good. I'll go home, then ;)
Asger> We just need to make sure that "string", "LString" and
Asger> "wstring" are all valid strings, and each behave like a
Asger> standard C++ string. LString is either a "string" or a
Asger> "wstring", according to a compilation time flag (that we need
Asger> to add at some point. For now hardcoding LString to be 8-bit is
Asger> necessary, because we have not transfered the source code to
Asger> the new string setup.)
What remains to to is provide a correct 16bit LString replacement, right?
Asger> We need to change all the LStrings to ordinary "string"s.
I thought you wanted to keep LString? Do you mean you want to
reintroduce them later when needed?
Asger> So a search/replace should be able to do it, but it will require us
Asger> to synch up, because it'll affect basically all files in the
Asger> source code. Any ideas on how to do ease the impact of this
Asger> change?
Well, it is not as if major commits happened every day in cvs... I
think it can be done the obvious way.
JMarc
