From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GNU Make
Date: Wed, 2 Jun 2004 13:13:39 +0200 [thread overview]
Message-ID: <f884497a8f5ccfb72c05e70c3e14e652@proxima.alt.za> (raw)
> Messages and Codes was notoriously unhelpful in many cases.
Sure, but was the problem with the concept or with the implementation?
In my particular case, my concern lies largely with system library
functions, a finite error message space. In fact, given that a
significant portion of the errors are concurrent with 9P, it ought to
be trivial to rationalise at least those error messages into a finite
set.
I'm suggesting that discipline in the use of error messages would be
constructive and that one mechanism to encourage such discipline would
be the use of indexing. I appreciate that it then becomes difficult
to escape the enforced rigidity, but one can add the escape mechanism
a priori.
I actually fail to see any other disadvantages of a disciplined
approach. I do see very clearly where the Plan 9 approach becomes a
nightmare.
++L
next reply other threads:[~2004-06-02 11:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 11:13 lucio [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 16:24 Trickey, Howard W (Howard)
2004-06-02 16:31 ` lucio
2004-06-02 23:53 ` Dan Cross
2004-06-01 11:09 lucio
2004-06-01 16:37 ` boyd, rounin
2004-06-01 21:03 ` ron minnich
2004-06-01 21:09 ` boyd, rounin
2004-06-01 21:43 ` Russ Cox
2004-06-01 21:49 ` ron minnich
2004-06-01 22:03 ` Russ Cox
2004-06-01 22:08 ` boyd, rounin
2004-06-02 5:34 ` lucio
2004-06-02 7:36 ` Charles Forsyth
2004-06-02 9:07 ` John Murdie
2004-06-02 9:39 ` Charles Forsyth
2004-06-02 16:12 ` ron minnich
2004-06-02 16:24 ` lucio
2004-06-02 16:54 ` ron minnich
2004-06-02 16:56 ` boyd, rounin
2004-06-03 6:41 ` lucio
2004-06-03 8:49 ` Charles Forsyth
2004-06-03 9:16 ` boyd, rounin
2004-06-03 10:31 ` lucio
2004-06-03 14:53 ` Rob Pike
2004-06-03 15:01 ` boyd, rounin
2004-06-03 15:04 ` lucio
2004-06-03 15:16 ` Rob Pike
2004-06-03 15:33 ` rog
2004-06-03 15:40 ` boyd, rounin
2004-06-03 15:58 ` lucio
2004-06-03 15:40 ` lucio
2004-06-02 21:30 ` boyd, rounin
2004-06-02 8:54 ` Richard Miller
2004-06-02 9:17 ` lucio
2004-06-02 9:54 ` Charles Forsyth
2004-06-02 16:15 ` ron minnich
2004-06-02 17:00 ` Steve Simon
2004-06-03 5:14 ` lucio
2004-06-02 14:00 ` ron minnich
2004-06-02 14:36 ` C H Forsyth
2004-06-02 14:33 ` Charles Forsyth
2004-06-02 15:24 ` Charles Forsyth
2004-06-02 15:56 ` lucio
2004-06-02 16:11 ` lucio
2004-06-02 19:28 ` Joel Salomon
2004-06-03 1:57 ` a
2004-06-03 3:31 ` Kenji Okamoto
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=f884497a8f5ccfb72c05e70c3e14e652@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).