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 12:47:11 +0200 [thread overview]
Message-ID: <20040106124711.K28128@cackle.proxima.alt.za> (raw)
In-Reply-To: <078bf5b96dbd23d46139b5fb8d927e8f@terzarima.net>; from Charles Forsyth on Tue, Jan 06, 2004 at 10:29:18AM +0000
On Tue, Jan 06, 2004 at 10:29:18AM +0000, Charles Forsyth wrote:
>
> the error numbers can never be relied upon;
> that's why they've got symbolic names
> (except in NFS where a subset is assigned specific numbers
> corresponding to the Sun errno assignment of the time,
> that often differ from those on the communicating systems,
> requiring errno swizzling)
Thanks, Charles.
Hm, in other words, I may as well start working on porting the
socket code I am working on to Plan 9, rather than make adjustments
for the missing error codes (EWOULDBLOCK and ECONNRESET).
That may make the next question redundant: many socket functions
are prototyped in APE with "int *len" as their last argument.
These days, in NetBSD these use soclen_t which is normally a uint,
but I think provision has been made for an int in some special
instances (I think it's a platform issue).
Does anyone know if the POSIX spec has changed to use "uint *len"
instead of "int *len" in the recent past (since the APE modules
were written)? Or "socklen *len" or "size_t *len" as I have seen
all of these on occasion?
++L
next prev parent reply other threads:[~2004-01-06 10:47 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 [this message]
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
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=20040106124711.K28128@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).