errno issues.

[Stefan Burstroem]

In article <199808240128.TAA19093 at sal.cs.utah.edu> you wrote:

> Instead of making errno a thread-local variable, which is what you seem
>to be suggesting, I think it would be better to make the functions that form 
>the syscall interface thread-safe.  I.e., instead of 
>	int read(int, void *, size_t)
>use
>	int read(int, void *, size_t, size_t *actual)
>that returns 0 on success and errno otherwise.

Yes, but this breaks all native functions that can be written too. Ie
if someone writes a native library they have to be very carefull about
errno. (Also, this requires all sys calls in Kaffe to be rewritten)

regards, Stefan Burstroem

-----------------------------------------------------------------------
>> Irl: Stefan Burstroem <<  >> Omnipresence Intl. <<  >> Irc: Yabba <<
 >> Phone: +46 (0)46-211 40 84 << >> EMail: stefan at omnipresence.com <<
-----------------------------------------------------------------------