[Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer

2010-09-10 Thread don dot wakefield at gmail dot com
--- Comment #6 from don dot wakefield at gmail dot com 2010-09-10 14:06 --- Re: comment 5 - what is needed is for filebuf::seekoff(0,ios::cur) to: 1) *not* invalidate the buffer 2) *not* move the file pointer since all that special case asks is "where am I in the 'log

[Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer

2010-09-10 Thread don dot wakefield at gmail dot com
--- Comment #8 from don dot wakefield at gmail dot com 2010-09-10 14:54 --- Paolo, yes, _M_file.seekoff(0,cur) would return the current physical file position, and then filebuf::seekoff would adjust the returned pos_type to reflect the position within the *logical* file, framed by the

[Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer

2010-09-10 Thread don dot wakefield at gmail dot com
--- Comment #10 from don dot wakefield at gmail dot com 2010-09-10 15:15 --- (In reply to comment #9) > Ok. I don't think we should change the code to deal such specially with off == > 0, if we are going to change it we should decouple the return value from what > the u

[Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer

2010-09-10 Thread don dot wakefield at gmail dot com
--- Comment #12 from don dot wakefield at gmail dot com 2010-09-10 15:24 --- (In reply to comment #11) > Sure. What I meant - contrary to wait you said, I think - is that an elegant > and complete solution to this issue involves changing much more generally our > code t

[Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer

2010-09-17 Thread don dot wakefield at gmail dot com
--- Comment #52 from don dot wakefield at gmail dot com 2010-09-17 21:11 --- (In reply to comment #51) > ...As a matter of fact, many users found it also quite easy to > use, because - in case wasn't clear already from my previous comments - > **nobody ever** complained