RE: wstring & wfstream

RE: wstring & wfstream

[Eric Ray]

One more thing.  Can anyone shed some light on why the typdef for
wstring is commented out.  This is the entire contents of the string
file.

--------------------------
// Main header for the -*- C++ -*- string classes.

#ifndef __STRING__
#define __STRING__

#include <std/bastring.h>

extern "C++" {
typedef basic_string <char> string;
// typedef basic_string <wchar_t> wstring;
} // extern "C++"

#endif

--------------------------

-----Original Message-----
From: Eric Ray 
Sent: Friday, March 15, 2002 10:45 AM
To: 'gcc-help@gcc.gnu.org'; 'gcc-patches@gcc.gnu.org';
'gcc-bugs@gcc.gnu.org'
Subject: wstring & wfstream


Two questions:

1. Why is there no wstring, wostream, wfstream, wofstream support in
g++?

2. How do I get wstring, wostream, wfstream, wofstream support in g++?

I've done a ton of searching on the net, so please, no referrals to
www.google.com or http://gcc.gnu.org/faq.html.  I've read the FAQ and
it's no help.  I've also searched the archives at http://gcc.gnu.org and
at http://gcc.gnu.org/libstdc++/.  

The only posting that is remotely close to what I'm looking for is this
one: http://gcc.gnu.org/ml/gcc-bugs/2001-11/msg00011.html.  This archive
talks about rebuilding g++ with the --disable-C99 configure option.
However, the authors post didn't make much sense to me and some of the
scripts he referred to do not exist.

I'm really stuck here and need wstring support for i18n and l10n issues.
Any advice or pointers would be greatly appreciated.  Thanks


Eric Ray 

Re: wstring & wfstream

[Phil Edwards]

On Fri, Mar 15, 2002 at 11:31:27AM -0600, Eric Ray wrote:
> One more thing.  Can anyone shed some light on why the typdef for
> wstring is commented out.  This is the entire contents of the string
> file.
> 
> --------------------------
> // Main header for the -*- C++ -*- string classes.
> 
> #ifndef __STRING__
> #define __STRING__
> 
> #include <std/bastring.h>

Anything involving "bastring.h" is using GCC 2.x, which doesn't support
wide I/O very well if it all.  You should use GCC 3.x, which uses a
completely rewritten C++ library and supports wide I/O on those systems
where it's available.

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

wstring & wfstream

[Eric Ray]

Two questions:

1. Why is there no wstring, wostream, wfstream, wofstream support in
g++?

2. How do I get wstring, wostream, wfstream, wofstream support in g++?

I've done a ton of searching on the net, so please, no referrals to
www.google.com or http://gcc.gnu.org/faq.html.  I've read the FAQ and
it's no help.  I've also searched the archives at http://gcc.gnu.org and
at http://gcc.gnu.org/libstdc++/.  

The only posting that is remotely close to what I'm looking for is this
one: http://gcc.gnu.org/ml/gcc-bugs/2001-11/msg00011.html.  This archive
talks about rebuilding g++ with the --disable-C99 configure option.
However, the authors post didn't make much sense to me and some of the
scripts he referred to do not exist.

I'm really stuck here and need wstring support for i18n and l10n issues.
Any advice or pointers would be greatly appreciated.  Thanks


Eric Ray