Home/ Questions/Q 8100437
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T22:44:09+00:00

Is there any conceivable reason why I would see different results using unicode string

  • 0

Is there any conceivable reason why I would see different results using unicode string literals versus the actual hex value for the UChar.

UnicodeString s1(0x0040); // @ sign
UnicodeString s2("\u0040");

s1 isn’t equivalent to s2. Why?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The \u escape sequence AFAIK is implementation defined, so it’s hard to say why they are not equivalent without knowing details on your particular compiler. That said, it’s simply not a safe way of doing things.

    UnicodeString has a constructor taking a UChar and one for UChar32. I’d be explicit when using them:

    UnicodeString s(static_cast<UChar>(0x0040));

    UnicodeString also provide an unescape() method that’s fairly handy:

    UnicodeString s = UNICODE_STRING_SIMPLE("\\u4ECA\\u65E5\\u306F").unescape(); // 今日は
    • 0