SRFI 199: POSIX errno manipulation
Arthur A. Gleckler
(26 Jun 2020 02:31 UTC)
|
Re: SRFI 199: POSIX errno manipulation
John Cowan
(26 Jun 2020 02:39 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Marc Nieper-Wißkirchen
(26 Jun 2020 06:02 UTC)
|
Re: SRFI 199: POSIX errno manipulation
hga@xxxxxx
(26 Jun 2020 14:44 UTC)
|
Re: SRFI 199: POSIX errno manipulation Marc Nieper-Wißkirchen (26 Jun 2020 15:22 UTC)
|
Re: SRFI 199: POSIX errno manipulation
John Cowan
(27 Jun 2020 04:03 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Shiro Kawai
(27 Jun 2020 09:52 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Shiro Kawai
(27 Jun 2020 09:53 UTC)
|
Re: SRFI 199: POSIX errno manipulation
hga@xxxxxx
(27 Jun 2020 10:55 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Shiro Kawai
(27 Jun 2020 11:12 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Lassi Kortela
(27 Jun 2020 11:26 UTC)
|
Re: SRFI 199: POSIX errno manipulation
John Cowan
(27 Jun 2020 14:47 UTC)
|
Re: SRFI 199: POSIX errno manipulation
hga@xxxxxx
(27 Jun 2020 15:05 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Lassi Kortela
(27 Jun 2020 15:12 UTC)
|
Re: SRFI 199: POSIX errno manipulation
hga@xxxxxx
(27 Jun 2020 15:40 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Lassi Kortela
(27 Jun 2020 15:47 UTC)
|
Re: SRFI 199: POSIX errno manipulation
Shiro Kawai
(27 Jun 2020 17:51 UTC)
|
Re: SRFI 199: POSIX errno manipulation
John Cowan
(27 Jun 2020 15:49 UTC)
|
Am Fr., 26. Juni 2020 um 16:44 Uhr schrieb <xxxxxx@ancell-ent.com>: > And the step in-between of calling a POSIX function that only signals > an error by setting errno, like getpwnam and getpwuid and their group > versions. This is the severe danger, compared to calling a POSIX > function, getting an error return, and then checking errno and getting > a heisenbug value. Indeed. > Would not such a facility also have to be used by all the POSIX > calls that are used in concert with SRFI 199 (and 198, for raising > syscall-errors)? This could certainly be the Worse Is Better, New > Jersey Style method to solving this very real problem. What would > this look like? I haven't followed the discussions for SRFI 170 and SRFI 198, but it seems to me that exposing the errno concept is problematic. Better to deliver the error value as part of the Scheme versions of the POSIX functions. This can happen through different types being returned and through Either wrappers coming from SRFI 189. Marc