This is not a real defect report, as it affects the current draft
only.

Library issue #22 added footnotes 324 & 325, explaining that "A
successful open does not change the error state" of the stream.

Issue #409, however, now says that a successful open() in fact DOES
call clear(), which resets the error state.

This is a contradiction.



Bo Persson


---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

In article <42kvuuF1jsr38U1@individual.net>, bop@gmb.dk ("Bo Persson")
wrote:

> This is not a real defect report, as it affects the current draft
> only.
>
> Library issue #22 added footnotes 324 & 325, explaining that "A
> successful open does not change the error state" of the stream.
>
> Issue #409, however, now says that a successful open() in fact DOES
> call clear(), which resets the error state.
>
> This is a contradiction.

Haven't you heard?  We're the standard with a sense of humor! :-)

Thanks Bo, I'll open an issue for this one.  At least you caught it
before the WD is set in stone. :-)

-Howard

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]