From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Lisp is a family quarrel
Date: Sat, 2 Aug 2014 10:28:17 -0400 [thread overview]
Message-ID: <20140802142816.GB15007@mercury.ccil.org> (raw)
In-Reply-To: <63E407A2-C677-4C73-A69F-02CDE5F68F36@tfeb.org>
Tim Bradshaw scripsit:
> And actually that's the only reason for needing a caps lock key really:
> for systems which *had* no lowercase, then you wouldn't need a caps
> lock key because you couldn't *type* lowercase!
As I said, it allows you to adjust to a mismatch: a keyboard that types
lower case by default, software that rejects lower case.
> (Lisp being more correctly thought of as a religion than a programming
> language).
"Do you know the saying, Karhide is not a nation but a family
quarrel?" I haven't, and suspect that Estraven made it up;
it has his stamp.
--Le Guin, _The Left Hand of Darkness_
Lisp, too, is a family quarrel. Scheme is even more so than Common Lisp;
CL is a language, but Scheme is a family of languages, perhaps 80 of them.
The minimalist R5RS standard of 1998 was case-folding, like all standards
before it, but perhaps half of all implementations ignored this and were
case-sensitive. In practice, case-folding implementations folded to lower
case, and where case was not folded, the standard identifiers were lower
case. The latter position is a feature of the case-sensitive R6RS (2007)
and R7RS-small (2013) standards. At present, case-sensitivity dominates
in the 40+ implementations that I use for test purposes by about two to one.
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
After fixing the Y2K bug in an application:
WELCOME TO <censored>
DATE: MONDAK, JANUARK 1, 1900
next prev parent reply other threads:[~2014-08-02 14:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:44 [TUHS] terminal - just for fun Tim Newsham
2014-07-31 22:59 ` Dave Horsfall
2014-08-02 13:30 ` random832
2014-08-01 9:00 ` Dario Niedermann
2014-08-01 15:13 ` Andy Kosela
2014-08-01 15:28 ` Milo Velimirović
2014-08-01 17:50 ` Mary Ann Horton
2014-08-01 17:59 ` Cory Smelosky
2014-08-01 19:59 ` Tim Newsham
2014-08-01 20:11 ` Dave Horsfall
2014-08-01 20:35 ` John Cowan
2014-08-02 1:49 ` Dave Horsfall
2014-08-02 3:27 ` Tim Bradshaw
2014-08-02 3:45 ` Greg 'groggy' Lehey
2014-08-02 9:24 ` Tim Bradshaw
2014-08-02 14:28 ` John Cowan [this message]
2014-08-03 6:47 ` Dave Horsfall
2014-08-04 18:04 ` scj
2014-08-04 18:18 ` Tim Newsham
2014-08-04 18:29 ` John Cowan
2014-08-04 19:10 ` Tim Newsham
2014-08-04 19:13 ` Milo Velimirović
2014-08-04 19:21 ` Tim Newsham
2014-08-04 18:28 ` John Cowan
2014-08-05 13:13 ` arnold
2014-08-05 14:20 ` John Cowan
2014-08-05 14:46 ` arnold
2014-08-04 20:15 ` Jaap Akkerhuis
2014-08-04 20:39 ` Dave Horsfall
2014-08-02 4:28 ` Dave Horsfall
2014-08-02 4:46 ` Warner Losh
2014-08-02 13:22 ` Nemo
2014-08-02 3:37 ` Greg 'groggy' Lehey
2014-08-02 5:45 ` Dave Horsfall
2014-08-02 6:09 ` Greg 'groggy' Lehey
[not found] ` <20140802061214.GC13625@mercury.ccil.org>
2014-08-02 6:17 ` Dave Horsfall
2014-08-02 13:35 ` Bill Pechter
2014-08-02 14:04 ` Milo Velimirovic
2014-08-03 2:00 ` Greg 'groggy' Lehey
2014-08-02 14:30 ` John Cowan
2014-08-01 21:32 ` Dario Niedermann
2014-08-01 21:38 ` Warner Losh
2014-08-01 21:56 ` Dario Niedermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140802142816.GB15007@mercury.ccil.org \
--to=cowan@mercury.ccil.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).