[r6rs-discuss] [Formal] Scheme should not be changed to be case sensitive.

From: Thomas Lord <lord>
Date: Thu Nov 16 12:45:59 2006

So, John, just to be clear, my complaint here is about
section 9.14 which says, of INTEGER->CHAR:

    (integer->char sv)

    Sv must be a scalar value, i.e., a non-negative
    exact integer in [0,#xD7FF] union [#xE000, #x10FFFF].

I would rather see:

    (integer->char sv)

    Implementations are permitted to require that
    Sv be a Unicode scalar value, i.e., a non-negative
    exact integer in [0,#xD7FF] union [#xE000, #x10FFFF].

Do you have any serious objections to such a change?
I understand that you might personally find such a
design unwise. You might even worry that such
an implementation (if its non-standard output started
to matter) could be "bad for Unicode" in some sense,
because now there would be new de facto encoding
forms. But are there any reasons to enforce such
misgivings via the Scheme standard?

-t
Received on Thu Nov 16 2006 - 12:46:13 UTC