I'm seeing messages here about issues where I would expect that the sender
wants to be sure that the issue gets addressed. Everybody please take a
moment to read the procedure described at
<
http://www.r6rs.org/process.html>. Note that if you want to be sure that
your concern is addressed, you must submit a formal comment. Just sending
mail to this list isn't good enough.
For typos you can probably count on the authors just picking them up from
here and correcting them -- but you wouldn't be too bummed out if your
typos were overlooked either. (After all, the final report will have a
typo or two no matter how hard we all try.)
But if you want to be sure that there is only a single eof object (in the
sense of eq?), or you don't like the way script exits codes are specified,
or you want a suite of flonum decomposition procedures. Then the only way
to be sure the authors don't just blow you off is to submit a formal
comment.
Of course you may be intending to submit a formal comment later, and just
want to talk it out here first. That's cool. I just wanted to make sure
that y'all understand how this is supposed to work.
- Alan
Received on Mon Sep 18 2006 - 22:39:20 UTC