From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] read of eof
Date: Tue, 21 Nov 2006 17:38:34 +1100 [thread overview]
Message-ID: <775b8d190611202238o6b5e0cefr98a6ec126bd7bdf0@mail.gmail.com> (raw)
In-Reply-To: <AC6A4931-280A-439A-98B0-F3EA320E1B76@cibernet.com>
This is crap - we are talking about delimitered messages.
But say what you like, no one listens.
brucee
On 11/21/06, Michael Baldwin <michael@cibernet.com> wrote:
> Obviously, a read of end-of-file should return -42. And if the data
> is possessed, -666.
>
> Seriously, there were two languages that I thought integrated
> exceptions / failures well enough that you could actually use them
> all the time pleasantly: Icon and Mesa. System calls (or expressions)
> would "fail" instead of return in-band values, and the syntactic
> sugar was light enough on calories that you didn't have the sense
> that you were dragging out an exception handling harness with whipped
> cream on top all the time just for one little call.
>
> Ah well.
>
>
next prev parent reply other threads:[~2006-11-21 6:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 19:06 [9fans] v9fs mounting in linux Paul Lalonde
2006-11-20 19:15 ` erik quanstrom
2006-11-20 22:35 ` Paul Lalonde
2006-11-21 0:27 ` ron minnich
2006-11-21 1:16 ` Paul Lalonde
2006-11-21 2:36 ` ron minnich
2006-11-21 2:42 ` Paul Lalonde
2006-11-21 2:49 ` ron minnich
2006-11-21 3:00 ` erik quanstrom
2006-11-21 3:17 ` [9fans] read of eof Michael Baldwin
2006-11-21 6:38 ` Bruce Ellis [this message]
2006-11-21 1:23 ` [9fans] Re: echo -n arisawa
2006-11-21 2:32 ` ron minnich
2006-11-21 17:36 ` Andrew Lynch
2006-11-21 17:35 ` andrey mirtchovski
2006-11-21 18:13 ` Axel Belinfante
2006-11-21 18:23 ` andrey mirtchovski
2006-11-21 18:31 ` Axel Belinfante
2006-11-21 18:53 ` Skip Tavakkolian
2006-11-22 1:32 ` dmr
2006-11-24 4:17 ` Lyndon Nerenberg
2006-11-24 16:24 ` Bruce Ellis
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=775b8d190611202238o6b5e0cefr98a6ec126bd7bdf0@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).