This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
RE: Strange behaviour of "cin"
- From: "Arun Saini , Gurgaon" <arun at ggn dot hcltech dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 19 Feb 2002 18:02:46 +0530
- Subject: RE: Strange behaviour of "cin"
> I'm moving this over to the libstdc++ list: there is no
> reason to keep it
> on both gcc and libstdc++.
Ok. I wasn't sure if it was a problem with libstdc++ or gcc so I sent it to
both.
> > I am sorry I should have mentioned it again, I did that in
> >my initial mail.
> > I am using gcc 3.0.3 on SCO 5.0.5.
> > Is this a peculiar behaviour on SCO or is gcc not able to
> *fix* this header
> > correctly. I suspect the reason to be
> > the inline definitions, and there corresponding macro
> definitions, for
> > various type identification functions present
> > in the <ctype.h> header. These are over-ridden if we use <cctype>.
>
> You'll probably need to add SCO-specific ctype bits. See
> libstdc++-v3/config/os/*/bits/ctype_*
1. Do you intend to incorporate the SCO specific ctype bits into libstdc++
in the near future? If not, can you give me some pointers about what it
really contains.
2. If I write this, how do I make the rest of the code aware that I have
added this there?
Arun