From: "David J. Fiander" <david@golem.uucp>
To: ronald@robobar.co.uk (Ronald S H Khoo)
Cc: rc@archone.tamu.edu
Subject: Re: A lighter read function
Date: Thu, 12 Dec 1991 06:16:35 -0600 [thread overview]
Message-ID: <24993.692540195@golem.UUCP> (raw)
In-Reply-To: Your message of "Wed, 11 Dec 91 16:48:50 EST." <9112112148.AA05916@robobar.Co.Uk>
>From: ronald@robobar.co.uk (Ronald S H Khoo)
>
>This looks wrong to me. line(1) does not use stdio. Where available,
>line(1) should preserve the seek position of the stream so that anyone
>who comes afterwards can read the rest. Trying to fseek back there
You're right. I thought of this during the trip to work on the
subway. But then, that will make the line binary even smaller.
- David
next prev parent reply other threads:[~1991-12-12 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-12-11 4:32 DaviD W. Sanderson
1991-12-11 12:28 ` David J. Fiander
1991-12-11 19:28 ` Chris Siebenmann
1991-12-13 0:58 ` David J. Fiander
1991-12-13 1:37 ` Chris Siebenmann
1991-12-13 1:47 ` David Hogan
1991-12-11 21:48 ` Ronald S H Khoo
1991-12-12 12:16 ` David J. Fiander [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-12-11 3:53 David J. Fiander
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=24993.692540195@golem.UUCP \
--to=david@golem.uucp \
--cc=rc@archone.tamu.edu \
--cc=ronald@robobar.co.uk \
/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).