On Sunday 05 March 2006 11:46, Nicholas Clark wrote: > On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote:
> [It's worth considering making all the network I/O opcodes use a > consistent way of marking errors. At the moment, all return an integer > status code except for C<socket>, C<sockaddr>, and C<accept>.] > > IIRC the Linux kernel uses negative values as return codes, where these > values are the negation of the value errno would hold. If we can use simple > numeric values to cover all possibilities, this seems like a good approach, > as it avoids thread local issues with errno, and issues such as whether > return values are in errno, h_errno, or returned by the call itself > (C API for system calls, hostname lookups, threading calls respectively) Parrot, not being C, does have exceptions.... -- c
