Closed Bug 523156 Opened 15 years ago Closed 11 years ago

Investigate conditionally adding |typedef char16_t jschar| (and thus |-std=c++0x|) for supporting compilers

Categories

(Core :: JavaScript Engine, enhancement)

Product:
Core
Component:
JavaScript Engine
Platform:
All
Linux
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 895047

People

(Reporter: Waldo, Assigned: Waldo)

References

Details

Unfortunately it seems U"foobar" tokenizes differently in C++98 and C++0x, so we have to opt the compiler in to compiling with support for Unicode strings, but that problem is surmountable, if complicating.  Being able to print jschar and jschar* would be sweet.
Depends on: 796948
See Also: → 895047
We have mozilla/Char16.h which gives us MOZ_UTF16 and char16_t. As an experiment, I #include'd that header and changed the typedef to see who fails:

* HashString(char16_t *) doesn't exist.
* The intl/ API has a mismatch of char16_t versus its internal type. It does allow you to provide a UCHAR_TYPE to specify exactly what you want to make it, though.
* Template helpers in TypeTraits.h don't exist.

Ameliorating these three issues is enough to move on to building xpcom, where the world breaks due to PRUnichar != jschar.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.