From: John Cowan <email@example.com>
Date: Sunday, October 06, 2019 10:07 AM
One thing I don't understand is the errno-error stuff. Why does it take a procedure object?
It shouldn't. Blame that on Olin's bad drafting compounded by my misreading. He wrote "syscall" and I changed that to "procedure". What it really is, per scsh-0.7, is a string containing the *name* of the procedure. I've fixed it now, with the consequence that syscall-error:procedure is replaced by syscall-error:procname. Note that this may be the name of a lower-level procedure called by the exported procedure.
Are we still planning on breaking all this out to a separate "system errors" SRFI? Besides our using POSIX errnos for our own error reporting such as bad arguments, I want another string to indicate where the error occurred, e.g. which argument is bad.
I've pushed this change, along with Harold's current changes to master, to https://github.com/johnwcowan/srfi-170
. I can file a pull request on the official SRFI if Harold thinks we're ready for that.
There are 9 commits you can first pick up from the official master, a couple which change the HTML file, and my addition of the Chibi Scheme example implementation, which:
Please adjust your implementations appropriately.
I then need to patch for this change.