From: mike@majestix.cs.uoregon.edu mike@majestix.cs.uoregon.edu
Subject: sfio vs bio
Date: Mon, 5 Jul 1993 13:20:25 -0400 [thread overview]
Message-ID: <19930705172025.yoE9OX7MqjsBSP1OV-eRetgjH9Lbi3OwNgTDhRIfdD8@z> (raw)
>Sfio has more facilities, e.g. you can define error handlers for
>streams, and can make use of operating system facilities like memory
>mapped files.
Sfio is also 7000 (10000 if you count stdio compatibility) lines of
code, whereas bio is about 700. Sfio is not 10 times faster or 10
times more useful. You're comparing apples to kumquats.
next reply other threads:[~1993-07-05 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-07-05 17:20 mike [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-07-05 10:06 Icarus
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=19930705172025.yoE9OX7MqjsBSP1OV-eRetgjH9Lbi3OwNgTDhRIfdD8@z \
--to=mike@majestix.cs.uoregon.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).