From: Joel Salomon <chesky@plan9.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] echo -n
Date: Mon, 20 Nov 2006 14:57:10 -0500 [thread overview]
Message-ID: <5c2bf4a5c8ff68ef5e1bfd2db024e300@plan9.jp> (raw)
In-Reply-To: <8ccc8ba40611201116r89eba04m32cf9d487a02ceb5@mail.gmail.com>
> > The only real solution is to change the interface so that
> > end-of-file is not signaled by a zero-length read. But that
> > convention is far too entrenched to go anywhere any time soon.
>
> Isn´t it that a write of zero bytes should just not write, instead
> of meaning a write of zero bytes?
>
> Or did I miss something?
That seems to be the definition under the Unix. From the Single UNIX
Specification, version 2 man page for write():
If nbyte is 0, write() will return 0 and have no other results
if the file is a regular file; otherwise, the results are
unspecified.
SUS3 is more verbose, but seems to have the same intent. Does Plan 9 use zero-length writes for something that shouldn’t be changed?
--Joel
next prev parent reply other threads:[~2006-11-20 19:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 8:40 arisawa
2006-11-20 9:45 ` Martin Neubauer
2006-11-20 10:42 ` lucio
2006-11-20 17:35 ` maht
2006-11-20 12:46 ` Russ Cox
2006-11-20 14:41 ` John Stalker
2006-11-20 14:59 ` Dave Lukes
2006-11-20 14:59 ` Axel Belinfante
2006-11-20 15:34 ` ron minnich
2006-11-20 15:43 ` erik quanstrom
2006-11-20 16:37 ` Joel Salomon
2006-11-20 18:49 ` Russ Cox
2006-11-20 19:16 ` Francisco J Ballesteros
2006-11-20 19:57 ` Joel Salomon [this message]
2006-11-20 20:18 ` Federico Benavento
2006-11-20 20:38 ` Russ Cox
2006-11-20 21:00 ` Joel Salomon
2006-11-20 21:05 ` Francisco J Ballesteros
2006-11-20 21:55 ` Russ Cox
2006-11-20 22:11 ` Francisco J Ballesteros
2006-11-20 22:24 ` Martin Neubauer
2006-11-20 23:14 ` Gorka guardiola
2006-11-20 23:22 ` Francisco J Ballesteros
2006-11-20 23:57 ` Gorka guardiola
2006-11-21 3:24 ` lucio
2006-11-20 19:32 ` Joel Salomon
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=5c2bf4a5c8ff68ef5e1bfd2db024e300@plan9.jp \
--to=chesky@plan9.jp \
--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).