Subject: Re: CLisp case sensitivity
From: rpw3@rpw3.org (Rob Warnock)
Date: Thu, 06 Jan 2005 21:57:37 -0600
Newsgroups: comp.lang.lisp
Message-ID: <1uGdnbf_U4gslUPcRVn-pg@speakeasy.net>
Cameron MacKinnon  <cmackin+nn@clearspot.net> wrote:
+---------------
| Tim Bradshaw wrote:
| > Has it stopped anyone interfacing with
| > Studly-by-default languages? No, of course it hasn't (I mean, even if
| > you're generating the interface manually, it really isn't that hard to
| > type |Foo| is it?  And are you *actually* generating the interface
| > manually? Surely you're not, and surely, like me you have utilities
| > which convert fooBar to foo-bar and FooBar to !foo-bar (if you need
| > the distinction)).
| 
| This is the "before" discussion. For software engineering practice
| like  this, the "after" discussion is held in comp.risks
+---------------

Indeed. Except that the only problem is that -- at least, based on the
case sensitivity discussions I've seen around here -- it's hard to guess
ahead of time which side(s) of the argument(s) will turn out to generate
the greater RISKs in the long run!!  ;-}  ;-}  [or maybe :-( ]

Seriously, I've seen cogent arguments in several directions, each of
which points out a RISK of some other direction than the "favored" one.
From all of this, the only thing I can take away with some confidence
is: "Be afraid.  Be *very* afraid."  [Or at least be very careful...]


-Rob

-----
Rob Warnock			<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607