Just noticed that SRFI 198's errno-error takes a symbol as the syscall-name, not a string.  While fixing up my Chibi Scheme SRFI 170 sample implementation to reflect this, I noticed the latter's HTML specifies the procedure symbol accessor as syscall-error:procedure, not the syscall-error:procedure-name of SRFI 198.

And while we're at it, why don't we add to the SRFI 198 API and SRFI 170 text syscall-error:syscall-name?  We're handing that to errno-error as a separate argument, but per the SRFI 198 language it could be completely ignored, and at best right now it can be embedded as a string in syscall-error:message.

Besides the above, I have no new observations to make about the current fully fleshed out SRFI 198, I'm ready to add a Chibi Scheme implementation to it as soon as the above suggestion for adding syscall-error:syscall-name is addressed.

Note I've got syscall-name fixed for SRFI 170, but will wait on resolution of the above suggestion before making another "final" pull request.

- Harold