From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Why does pread(2) modify the channel offset?
Date: Sun, 21 Jun 2015 13:35:40 +0100 [thread overview]
Message-ID: <CAOw7k5iTGRaa1tXeB+xCNFcjvLS-ksyinVNZAUeLkWY8Hc8ZmQ@mail.gmail.com> (raw)
In-Reply-To: <20150621104444.GA7504@dinah>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
On 21 June 2015 at 11:44, Anthony Martin <ality@pbrane.org> wrote:
> Thoughts?
As with programming language specifications, when it says "equivalent" it
is ignoring any subtle differences.
Neither call is supposed to change the offset, although it wasn't noticed
for the reason you gave.
One exception is reading directories, where pread should act the same as
read.
[-- Attachment #2: Type: text/html, Size: 766 bytes --]
prev parent reply other threads:[~2015-06-21 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 10:44 Anthony Martin
2015-06-21 12:35 ` Charles Forsyth [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=CAOw7k5iTGRaa1tXeB+xCNFcjvLS-ksyinVNZAUeLkWY8Hc8ZmQ@mail.gmail.com \
--to=charles.forsyth@gmail.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).