Daniel Bratell wrote:
> Jon Smirl wrote:
>
>> Thanks for the pointers I still hadn't noticed nsDependentString.
>>
>> Changing from PRUnichar* to the new interfaces is making me rewrite a
>> lot of
>> code. Passing in a nsAWritableString instead of a PRUnichar** changes
>> where
>> the string allocation takes place.
>
> Don't know anything about null strings (DOM strings) but I think the
> current fashion is to use nsAString even if it happens to be the exact
> same thing as nsAWritableString. nsAReadableString would then be a const
> nsAString I guess.
The concept of null strings is a work in progress.
typedef const nsAString nsAReadableString;
typedef naAString nsAWritableString;
At some point we should probably do a mass sweep and get rid of
nsAReadableString and nsAWritableString so we get rid of this confusion.
Does your interface really need to support null strings or can you (/ would it
be better to) express the lack of a string value through other means?
jag
