[comp.lang.c++] iostream behaviour

leo@atcmp.nl (Leo Willems) (06/30/90)

The new iostream library behaves rather strange:

	filebuf fb;
	fb.open("", in);

will connect fb to the current directory!

Is this ment to be?

(We use C++ 2.0 from Glockenspiel, a beta release for Sun sparc station,
they added there own iostream headerfile, but I don't know if they
changed the original iostream source.)

Thanks.

P.S.
iostream is very nice, compared to stream.
It also is fun, try this:

	main() { cout << cin.rdbuf();  }



 Leo Willems			Internet: leo@atcmp.nl
 AT Computing			UUCP:     mcsun!hp4nl!kunivv1!atcmpe!leo
 P. O. Box 1428				
 6501 BK  Nijmegen		Phone:    +31-80-566880
 The Netherlands		Fax:	  +31-80-555887

ark@alice.UUCP (Andrew Koenig) (06/30/90)

In article <629@atcmpe.atcmp.nl>, leo@atcmp.nl (Leo  Willems) writes:

> The new iostream library behaves rather strange:

> 	filebuf fb;
> 	fb.open("", in);

> will connect fb to the current directory!

Berkeley-based systems consider the null string to be a valid
name for the current directory.  System V considers the null string
to be an invalid pathname.
-- 
				--Andrew Koenig
				  ark@europa.att.com