It appears that unget() calls the sungetc() on the streambuf class, and sets the badbit if streambuf is null.
I am guessing that if the implementation chooses to set the streambuf to null after a seekg() (because no characters have been read), then calling unget() would set the badbit. If this is true, then the other compilers may be not changing the buffer after a seekg(), and clang 5 has now decided to be more strict, perhaps. -Manav On Mon, Oct 28, 2013 at 5:01 PM, Manav Bhatia <[email protected]> wrote: > >> Note that we are still calling unget(). The only thing I removed was an >> (apparently) redundant tellg/seekg pairing... >> > > Ahh... I see that I had missed your point. That is a good catch... and > thanks for clarifying! > > -Manav > ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
