This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Sun, Feb 14, 1999 at 10:56:33AM +0200, Harvey J. Stein wrote: >forcer <forcer@mindless.com> writes: > [(read-enable 'case-insensitive) has problems with predefined uppercase symbols] > > > > This means that guile *won't* see any variables that were defined > > upper-case *bevore* setting it case-insensitive. > >Not exactly. You just have to use the special syntax for using >upper case (or mixed case) symbols. I believe it's supposed to be >#{...}#, which should behave as: [snip] ... which can't be a solution. But i guess for this it would be valid (but a bit ugly) to state that the user should only redefine the case sensitivity in the beginning of a program, not in one. > > This also applies to all predeclared variables (SOL_SOCKET, etc.) > >Yes, those should probably be changed to lower case so that they're >easily & obviously accessible in general. It'd be best if all >pre-defineds are in the same case & (read-enable 'case-insensitive) >automatically maps to that case - i.e. - make everything upper case & >make read-enable map symbols to upper case, or make everything lower >case & make read-enable map to lower case. Changing them to lower-case would make guile incompatible with POSIX and, worse, with SCSH when it is in case-sensitive mode, so this can't be a solution either. It would be nice to change guile's symbol-matching to case-insensitivity, not only the reader, and special-case case-sensitive symbols, but i guess that OTT. -forcer -- ((email . "forcer@mindless.com") (www . "http://webserver.de/forcer/") (irc . "forcer@#StarWars (IRCnet)") (pgp . "key available on my website"))