> What remains to to is provide a correct 16bit LString replacement, right?
Yes.
> 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?
I want to keep LString, but only use it
>> Asger K Alstrup Nielsen writes:
AKAN> We need to change all the LStrings to ordinary "string"s. So a
AKAN> search/replace should be able to do it, but it will require us
AKAN> to synch up, because it'll affect basically all files in the
AKAN> source code. Any ideas on how to do ease t
> "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 a
> So, what magic should we add in there, besides defining a proper
> wstring based on LString?
Nothing.
We just need to make sure that "string", "LString" and "wstring" are
all valid strings, and each behave like a standard C++ string.
LString is either a "string" or a "wstring", according to a
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> [Definitions of LString, string and wstring.]
>> Why not do it directly in LString.h? It already contains some black
>> magic anyway.
Asger> Yes, let's do that. I'll do it right now, and trust somebody
Asger> to add the
[Definitions of LString, string and wstring.]
> Why not do it directly in LString.h? It already contains some black
> magic anyway.
Yes, let's do that. I'll do it right now, and trust somebody to
add the necessary magic.
Greets,
Asger
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> In the C++ standard, the definitions that you get with the
Asger> "#include " directive are all encapsulated in the "std"
Asger> namespace.
Asger> Namespaces are relatively new to the C++ language. They allow
Asger> you d
On Sun, 14 Mar 1999, Asger Alstrup Nielsen wrote:
[...namespaces...]
> When it comes to the compilers in these days, it seems the gcc family is not up
> to speed yet. I think the egcs 1.1 line has the proper support for namespaces,
> but the standard C++ library is not standard compliant yet.
>
