9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/include/ape/errno.h
Date: Tue,  6 Jan 2004 19:24:01 +0200	[thread overview]
Message-ID: <20040106192401.A5956@cackle.proxima.alt.za> (raw)
In-Reply-To: <E1AdrDL-000JNk-Ng@t40.swtch.com>; from Russ Cox on Tue, Jan 06, 2004 at 08:25:42AM -0500

On Tue, Jan 06, 2004 at 08:25:42AM -0500, Russ Cox wrote:
>
> down that path lies madness.  use the names, that's what they're for.
> the numbers aren't supposed to matter!
>
I was looking for a standard definition, so that I could address:

	#define EPROTONOSUPPORT	37
	#define EPROTOTYPE 37

as found in /sys/include/ape/errno.h, which broke a module construct.
I wasn't suggesting that I wanted to use the numeric values instead.
I'm not sure how I want to solve the original problem, given that
Charles pointed out a similar duplication in Linux, was it?

	#define	EWOULDBLOCK	EAGAIN

or some such, from memory.

++L


  parent reply	other threads:[~2004-01-06 17:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 10:24 Lucio De Re
2004-01-06 10:29 ` Charles Forsyth
2004-01-06 10:47   ` Lucio De Re
2004-01-06 10:56     ` Charles Forsyth
2004-01-06 11:19       ` Lucio De Re
2004-01-06 12:30     ` David Presotto
2004-01-06 12:48       ` [9fans] Newbie Question: Plan 9 for a windows file server? Chris Lamrock
2004-01-06 13:03       ` [9fans] /sys/include/ape/errno.h Lucio De Re
2004-01-06 13:15         ` David Presotto
2004-01-06 13:25         ` Russ Cox
2004-01-06 15:04           ` Charles Forsyth
2004-01-06 17:24           ` Lucio De Re [this message]
2004-01-06 12:42 ` David Presotto
2004-01-06 12:59   ` Lucio De Re
2004-01-06 15:22 ` ron minnich
2004-01-06 16:41   ` Nigel Roles
2004-01-06 18:19 Richard C Bilson

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=20040106192401.A5956@cackle.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).