Paul Green <[EMAIL PROTECTED]> writes: >> How do you guarantee you'll never hit the code in >> PerlIOStdio_unread that does ungetc inside a loop? > >We will hit it. But it will fail after the first ungetc. > >We have hidden variables in the stream data structure that tell >us whether an ungetc is permitted. The ungetc function sets and >checks these hidden variables such that any attempt to do two >ungetc's in a row will cause subsequent ungetc's to return an >error.
Which seems overly picky if you not at begining of the buffer, why not allow ptr to back up and take as much as you are given? But perlio.c will soon not care :-) -- Nick Ing-Simmons http://www.ni-s.u-net.com/
