On Thu, Sep 19, 2019 at 4:54 PM Lassi Kortela <xxxxxx@lassi.io> wrote:
 
I can draft one if it doesn't matter that it may take a month. 

R7RS-large is a multiyear, possibly multi-decade design effort.  A month is nothing. 
 
The pet feature I'd like to have is retrieving errno values from
standard RnRS I/O procedures;

I'm not opposed in principle.  However, this will have to hook deeply into the Scheme implementation, and implementers will tend to resist things that do that, especially for implementations that care a great deal about backward compat.  The (non-)adoption of R6RS demonstrated that very clearly: the entirely new exception system was not something that any existing implementation was willing to adopt.  (A few did, but they often ended up with two parallel exception systems.)
 
II think libexplain was the name of that friendly-unix-errors library you
linked some time ago.

Yes.



John Cowan          http://vrici.lojban.org/~cowan        xxxxxx@ccil.org
Today an interactive brochure website, tomorrow a global content
management system that leverages collective synergy to drive "outside of
the box" thinking and formulate key objectives into a win-win game plan
with a quality-driven approach that focuses on empowering key players
to drive-up their core competencies and increase expectations with an
all-around initiative to drive up the bottom-line. --Alex Papadimoulis