From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Why doesn't bio have bscanf?
Date: Fri, 23 Sep 2005 08:39:28 -0700 [thread overview]
Message-ID: <C496463D-4DD6-4CED-9E08-6CB728A949BE@telus.net> (raw)
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. Why doesn't bio
have one? Given the right argument I can get the fscanf-dependent
parts reworked...
Thanks,
Paul
next reply other threads:[~2005-09-23 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 15:39 Paul Lalonde [this message]
2005-09-23 15:46 ` andrey mirtchovski
2005-09-23 15:59 ` Paul Lalonde
2005-09-23 15:51 ` 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=C496463D-4DD6-4CED-9E08-6CB728A949BE@telus.net \
--to=plalonde@telus.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).