Strange behaviour of "cin"
Mon Feb 18 10:00:00 GMT 2002
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
More information about the Libstdc++