| To: | Eric Christopher <echristo@redhat.com> |
|---|---|
| Subject: | Re: Changing WCHAR_TYPE from "long int" to "int"? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Tue, 7 Aug 2001 01:49:10 +0200 |
| Cc: | Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>, "H . J . Lu" <hjl@lucon.org>, gcc@gcc.gnu.org, linux-mips@oss.sgi.com, GNU C Library <libc-alpha@sourceware.cygnus.com> |
| In-reply-to: | <997108890.1773.22.camel@ghostwheel.cygnus.com>; from echristo@redhat.com on Mon, Aug 06, 2001 at 03:41:28PM +0100 |
| References: | <20010806164000.E400@rembrandt.csv.ica.uni-stuttgart.de> <997108890.1773.22.camel@ghostwheel.cygnus.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Mon, Aug 06, 2001 at 03:41:28PM +0100, Eric Christopher wrote: > Hrm. You might be right. I was thinking that would be correct though. > AFAICT from reading the c++ standard, it doesn't care about the size of > wchar_t as long as it is large enough to hold the values from the > supported locales. > > Perhaps some c++ expert could help with this a bit? Benjamin is there a > problem if wchar_t becomes 64-bits? On 64-bit MIPS ABI compliant machines I see wchar_t defined to __int32_t which again is int. Ralf |
| Previous by Date: | Re: set_bit() function., Ralf Baechle |
|---|---|
| Next by Date: | null TTY error, kjlin |
| Previous by Thread: | Re: cross-mipsel-linux-ld --prefix library path, Steve Langasek |
| Next by Thread: | Re: Changing WCHAR_TYPE from "long int" to "int"?, H . J . Lu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |