This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: in_avail() error. Major compliance problem


On Sunday 28 October 2001 01:10, Florian Weimer wrote:
> David Rasmussen <pinkfloydhomer@yahoo.com> writes:
> > #include <iostream> int main()
> > {
> > 	std::cout << std::cin.rdbuf()->in_avail() << std::endl;
> > 	return 0;
> > }
> >
> > This simple code should write a 0 and exit immediately. This is what
> > happens with gcc 2.95.3 and the library that comes with that. With gcc
> > 3.0.2, it is hanging blockingly until enter is pressed, and then writes a
> > 1.
>
> This behavior is probably correct as far as the C++ standard is
> concerned, I'm afraid.

How do you figure? in_avail shouldn't be blocking according to the standard. 
And it shouldn't return 1 always according to the standard.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]