Const correctness in input/output libraries

[nvitacolonna]

I have found this page:

http://www.open-std.org/jtc1/sc22/wg...2002/n1360.htm

identifying const-correctness inconsistencies in the input/output
standard libraries (e.g., tellg() not being declared const). I was
just wondering: what is the current opinion of the standard committee
about such issue? Is that going to be taken into account for the new
standard? (I admit that I was a bit surprised when I discovered that
is_open() and tellg() are not const).

Nicola

[=?UTF-8?B?RXJpayBXaWtzdHLDtm0=?=]

On 2008-01-21 12:00, nv**********@gmail.com wrote:

I have found this page:

http://www.open-std.org/jtc1/sc22/wg...2002/n1360.htm

identifying const-correctness inconsistencies in the input/output
standard libraries (e.g., tellg() not being declared const). I was
just wondering: what is the current opinion of the standard committee
about such issue? Is that going to be taken into account for the new
standard? (I admit that I was a bit surprised when I discovered that
is_open() and tellg() are not const).

I can not speak for the standards committee but a quick check shows that
those functions are still not const in the current working draft. I can
see two reasons for this, the first being that since the proposal was
made before they started working on the new version it was forgotten.
The other alternative is that the proposal was considered but for some
reason it was rejected (perhaps it would break too much existing code?).
You can try asking asking in comp.std.c++.

--
Erik Wikström