On 10/3/21 02:45, Marc Nieper-Wißkirchen wrote:

I asked for you motivation for the change, and it seems like this is
your key concern:

> The way I read the current text of SRFI 37, it implies that
> implementations must support any option character (of the Unicode
> repertoire in R6RS+ implementations).

I don't think your concern is warranted. The specification does not
require you to support the Unicode repertoire of R6RS+, in fact, the
specification was written under R5RS, so go ahead and write your
implementation which enforces the strict POSIX guidelines, but your
users will be unhappy if use Unicode to justify breaking their ASCII
'-?' option which has worked fine for almost 20 years.

--
Anthony Carrico