From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7871fcf50702141658g5e5b6096t2100eb42b617edff@mail.gmail.com>
Date: Wed, 14 Feb 2007 19:58:20 -0500
From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Repeated Bungetc or Bungetrune
In-Reply-To: <8faae81e6679b9206db550503c8d44a2@plan9.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8faae81e6679b9206db550503c8d44a2@plan9.jp>
Topicbox-Message-UUID: 10da402c-ead2-11e9-9d60-3106f5b1d025

> For this case anyway, where I know that the Rune read was a
> single-byte character, is it safe to use Bungetc, and will that allow
> me to back-up more than once?  I need (I think) three bytes of
> back-up.

I've tried it, and (on a small test case) nothing broke; 'long' is
recognized as the keyword rather than the identifier 'ong'.  I just
would like some reasurrance from someone who knows the bio code
better.

Also, after Beof is read, does Bunget* have any meaning?

--Joel