The POSIX SRFI 170 at this time has a errno (https://pubs.opengroup.org/onlinepubs/9699919799/functions/errno.html) based exception system, which John has realized is inadequate for the task.  For example, we need to with clarity raise errors that don't come from system or library calls, such as when we detect that a SRFI 170 procedure is handed an invalid argument.  So John is planning on breaking that out into its own SRFI as he's done with the POSIX timespec SRFI 174.

Would it make sense to turn that into a general "systems errors" SRFI, for "arbitrary" errors from alien technology stacks like SRFI 170's POSIX, and myriad databases for us?  And have John's Simple SQL, my DBI, etc. use it?

- Harold