-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/10/2012 01:51 AM, John Cowan wrote:
>> Maybe a whitelist of characters that are definitely allowed
>> in symbols?
>
> There is such a list (of ASCII characters only) in 2.1.

Don't forget that string->symbol exists, and if it doesn't live by the
same restrictions, will be capable of generating symbols that can't be
represented with WRITE. And if it does live by those restrictions, it'll
be faintly annoying that strings and symbols aren't symmetrical.

I'd prefer that ALL characters are legal in symbols, and we carefully
distinguish "allowed in symbols" and "allowed unescaped in the written
representation of symbols" (bearing in mind that a written symbol from a
full Unicode system might be read in by an ASCII-only system) in
discussion :-)

The text on identifiers in 2.1 says that . is not an identifier; does
that mean I *cannot* write (define |.| 123) and then (+ |.| 456)?

I find the distinction between the abstract syntax of Scheme and its
written syntax a bit unclear :-(

If I get a moment I will carefully read all relevant sections of the
report and suggest some fixes...

ABS

- --
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8MFIsACgkQRgz/WHNxCGrz1gCfQ/n4fnAab/CjTHrrIIfOn1bE
JAwAmQEkcRW+UQr7smj1TmjGb02ayBzk
=ihe0
-----END PGP SIGNATURE-----

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports