From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bungetc error
Date: Thu, 3 Jan 2008 00:24:54 +0000 [thread overview]
Message-ID: <fed8baa1ca956b47ae30f82a00b1c513@terzarima.net> (raw)
In-Reply-To: <20080102215128.GB810@shodan.homeunix.net>
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
i assumed the intention was:
in practice it's sometimes a nuisance to have to keep a flag in the
application to say whether eof has been reached or not,
when it could be done by allowing an unget at eof.
[-- Attachment #2: Type: message/rfc822, Size: 3824 bytes --]
From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] bungetc error
Date: Wed, 2 Jan 2008 22:51:28 +0100
Message-ID: <20080102215128.GB810@shodan.homeunix.net>
* smahapatra_ct@yahoo.com (smahapatra_ct@yahoo.com) wrote:
> I think after bgetc returns Beof, bungetc should change the state, but
> not decrement bp->icount.
I don't think so. Bungetc ungets the last character read, not Beof.
prev parent reply other threads:[~2008-01-03 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 11:00 smahapatra_ct
2008-01-02 21:51 ` Martin Neubauer
2008-01-03 0:24 ` Charles Forsyth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fed8baa1ca956b47ae30f82a00b1c513@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).