9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] echo -n
Date: Tue, 21 Nov 2006 00:22:42 +0100	[thread overview]
Message-ID: <8ccc8ba40611201522g2514b38fn464a2b9d721daeeb@mail.gmail.com> (raw)
In-Reply-To: <599f06db0611201514u26ac129axa8b21894a17f6d00@mail.gmail.com>

Yes, but, what does it mean to write zero bytes?
I know, I know.
But my point is, does it make sense?
If you want a write of something weird to mean something, you might
just use a write of something weird, or a control operation kept appart.


A related question, can we create a file with an empty name?
Is what happens a bug or a feature?


On 11/21/06, Gorka guardiola <paurea@gmail.com> wrote:
> As I see it, the problem here is that of symmetry and special cases.
>
> A 0 read means eof. The problem is that it also means a 0 sized message on a
> pipe.
>
> There are 0 reads which are not eofs because we want to conserve
> the symmetry for pipes (n writes mean n reads) in order not add
> special cases. But then we have a special case when eof does not mean
> the pipe has been closed. Which is also an interpretation, because
> eof means end of file, but that means end of pipe or end of session or what?.
>
> So there is a compromise between the special case  of having zero
> writes, and thus not eof 0 reads which are not necessary because you
> can use a convention of a special character or something, versus
> adding a special case on the other side for the closing of pipes.
>
> So whatever you change, you are not better off so we stay put.
> Am I reading right or is there something else I am missing?.
>
> It is late and my english is fuzzy. Pardon my french.
> --
> - curiosity sKilled the cat
>
>


  reply	other threads:[~2006-11-20 23:22 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
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 [this message]
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=8ccc8ba40611201522g2514b38fn464a2b9d721daeeb@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).