[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: Doug Gregor <doug.gregor@xxxxxxxxx>, cxx-abi-dev@xxxxxxxxxxxxxxxx
Subject: Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
From: David Vandevoorde <daveed@xxxxxxx>
Date: Tue, 25 Mar 2008 12:08:51 -0400


On Mar 25, 2008, at 11:25 AM, Doug Gregor wrote:

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?

Fine by me, although I'd prefer something a little more "mnemonical";maybe W2 and W4.


	Daveed

Follow-Ups:
- Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
  - From: Jason Merrill
- Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
  - From: Michael Wong

References:
- C++0x: mangling of char16_t and char32_t
  - From: Doug Gregor

Prev by Date: C++0x: mangling of char16_t and char32_t
Next by Date: Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
Previous by thread: C++0x: mangling of char16_t and char32_t
Next by thread: Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t
Index(es):
- Date
- Thread

Actions

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