Actions

icon Post
text/html Subscribe
text/html Unsubscribe
CodeSourcery > List Archives
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t

  • To: cxx-abi-dev@xxxxxxxxxxxxxxxx
  • Subject: Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
  • From: David Vandevoorde <daveed@xxxxxxx>
  • Date: Wed, 26 Mar 2008 09:24:58 -0400

On Mar 25, 2008, at 10:29 PM, Dennis Handly wrote:

From: "Doug Gregor" <doug.gregor@xxxxxxxxx>
We don't have a mangling for the C++0x char16_t or char32_t types. It
has been suggested that we use 'k' for char16_t and 'q' for char32_t.
Does that seem reasonable?


I was thinking for HP-UX, char32_t would be the same as wchar_t.
It can be the same type from a back end perspective, but in C++ you can overload based on those types: 

	void f(wchar_t);   // (!)
	void f(char32_t);  // Different from (1)

So distinct encodings are needed.

	Daveed