Scheme Request for Implementation 198,
"POSIX system call exceptions,"
by John Cowan (editor and shepherd), Harold Ancell (implementer and
editor),
is now available for discussion.

Its draft and an archive of the ongoing discussion are available at <https://srfi.schemers.org/srfi-198/>.

You can join the discussion of the draft by filling out the subscription
form on that page.

You can contribute a message to the discussion by sending it to <srfi-198@srfi.schemers.org>.

Here's the abstract:

When POSIX system calls are mapped to Scheme exceptions, this small
SRFI provides the means to construct, signal, and extract information
from those signals in a reasonably uniform way. They are in their own
SRFI in order to avoid being tied to any single POSIX-based SRFI such
as SRFI 170.

Regards,


SRFI Editor

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

When POSIX system calls are mapped to Scheme exceptions, this small
SRFI provides the means to construct, signal, and extract information
from those signals in a reasonably uniform way. They are in their own
SRFI in order to avoid being tied to any single POSIX-based SRFI such
as SRFI 170.

Should this not rather be

When POSIX system call *errors* are mapped to Scheme exceptions, ...

(my emph)

--
Ian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thanks. John has now fixed this.

I just happened to notice your message here, but please send feedback on the SRFI mailing lists. That's what the authors, et al. monitor. For example, you can subscribe to SRFI 198's mailing list here:

http://srfi.schemers.org/srfi-198/


— SRFI Editor

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)