This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
RE: Strange behaviour of "cin"
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: "Arun Saini , Gurgaon" <arun at ggn dot hcltech dot com>
- Cc: "Andrea 'Fyre Wyzard' Bocci" <fwyzard at inwind dot it>, Joe Buck <jbuck at synopsys dot com>, libstdc++ at gcc dot gnu dot org
- Date: Mon, 18 Feb 2002 10:00:33 -0800 (PST)
- 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++.
> 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_*
-benjamin