Harald Hanche-Olsen <email@example.com> wrote:
| + Kent M Pitman <firstname.lastname@example.org>:
| | Note that the second of the two IN-SYNTAX forms _must_ be in
| | uppercase, while the others only optionally have to be. I'd do them
| | all in uppercase just to not have to remember it.
| You're assuming, of course, that the user is not perverse enough to
| use :invert, in which case the first form _must_ be in lowercase.
| (I am that perverse myself. I find it both astonishing and pleasing
| that this almost never causes any trouble in loading other people's code.)
Ditto. When "case-preserving" input is required, I consider :INVERT
to result in a *much* more "natural" human interface than the alternatives.
[I put "case-preserving" in quotes because what is usually *actually*
needed is not case-preserving-READ at all, but READ/PRINT-case-invariance
(as when reading/writing C variables as symbols), and for that purpose
:INVERT is really a better choice, since you can turn it on once and
leave it on...]
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607