From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Bgetrune while(i>runesize) loop
Date: Thu, 10 Jul 2008 16:18:13 -0400 [thread overview]
Message-ID: <36F38215-C75A-46DD-9287-006878D7A102@mac.com> (raw)
In-Reply-To: <20080710185217.6F0201E8C22@holo.morphisms.net>
I got nothing spectacular from that, but changing the \x00s to QRS
gave me something interesting: without the loop, readrune gives me
[?]S, but with it it, it gives me [?]QRS, like cat would've.
Would this be because fullrune doesn't check for validity, and if
chartorune fails then the possibility of eating too much comes about?
On Jul 10, 2008, at 2:53 PM, Russ Cox wrote:
>> Hello. I was looking at the code for the Bgetrune function trying to
>> implement a readrune() around read(). It works, but without a
>> counterpart for this:
>>
>> while(i > bp->runesize) {
>> Bungetc(bp);
>> i--;
>> }
>>
>> What is the point of that loop? Thanks.
>
> Use "\xE0\x00\x00" as your input and you will find out.
>
> Russ
>
>
next prev parent reply other threads:[~2008-07-10 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 18:13 Pietro Gagliardi
2008-07-10 18:53 ` Russ Cox
2008-07-10 20:18 ` Pietro Gagliardi [this message]
2008-07-10 20:45 ` Russ Cox
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=36F38215-C75A-46DD-9287-006878D7A102@mac.com \
--to=pietro10@mac.com \
--cc=9fans@9fans.net \
/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).