[Continuing from private mail]

Lassi:

> Hey, you added libsodium into the initial list of foreign status sets. Does that library have a predefined set of error codes? I can't find a set in the documentation or source. The functions just return 0 on success and -1 on failure.

Harold:

> No, it doesn't, and the lack of standard error codes is *exactly* why I included it in the examples. Compare to errnos and PostgreSQL standing in for any good SQL RDBMS, it's an example to show the opposite where the SRFI 198 user get a single return value (in the UNIX style) and has to do everything else himself.
>
> BTW, how's the localization discussion going? "I have no dog in that hunt", so I haven't been following it, but it's the blocker for the next draft (unless anyone brings it up again, I'm going to continue to eschew convenience calling of lambdas, I think the case against that is strong enough).
>
> Please also include this paragraph I just added to my copy of the SRFI document in https://github.com/hga/srfi-198 It's right after the currently not formatted table of sample error-sets:
>
> POSIX errnos are a generally familiar error system with a moderate degree of structure, and the initial inspiration for this SRFI. PostgreSQL is a representative SQL RDBMS with a richer set of error data that can be transmitted to the user, and its client/server organization is a useful counterpoint to getting an error through a FFI. libsodium has a typical simple UNIX™ style C API that returns 0 on success and -1 on error, and nothing more.