From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Why doesn't bio have bscanf?
Date: Fri, 23 Sep 2005 11:51:55 -0400 [thread overview]
Message-ID: <ee9e417a05092308514577d4cf@mail.gmail.com> (raw)
In-Reply-To: <C496463D-4DD6-4CED-9E08-6CB728A949BE@telus.net>
> I'm having to write (yet another) a buffered IO library (I hate
> hardware that comes with broken buffered IO libs....grrr) and was
> thinking of cribbing bio, but some of the code we need to run is
> quite dependent on (yuck) fscanf-style processing.
Starting with bio and writing bscanf on top seems
preferable to starting from scratch.
> Why doesn't bio have one? Given the right argument
> I can get the fscanf-dependent parts reworked...
I don't know, but the usual answer is that no one actually
wanted to use it. I know that even when it's available
and appropriate I don't use it because it makes it harder
to give good error messages about what didn't parse right.
For example, you have no idea which line you're on after
you've scanned " ".
Russ
prev parent reply other threads:[~2005-09-23 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 15:39 Paul Lalonde
2005-09-23 15:46 ` andrey mirtchovski
2005-09-23 15:59 ` Paul Lalonde
2005-09-23 15:51 ` Russ Cox [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=ee9e417a05092308514577d4cf@mail.gmail.com \
--to=rsc@swtch.com \
--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).