[slime-devel] Symbols in COMMON-LISP are all in UPPER CASE!
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP). So why can't we look up them in upper case? Let's ignore case when completing symbols in slime-hyperspec-lookup and everybody will be happy. (defun slime-hyperspec-lookup (symbol-name) "A wrapper for `hyperspec-lookup'" (interactive (list (let ((completion-ignore-case t) ;; <<<<--------- (symbol-at-point (slime-symbol-name-at-point))) (if (and symbol-at-point (intern-soft (downcase symbol-at-point) common-lisp-hyperspec-symbols)) symbol-at-point (completing-read "Look up symbol in Common Lisp HyperSpec: " common-lisp-hyperspec-symbols #'boundp t symbol-at-point 'common-lisp-hyperspec-history))))) (hyperspec-lookup symbol-name)) -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein
Pascal J.Bourguignon wrote:
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP).
No, not necessarily in all lisp impls. (e.g. AFAIK Allegro has a switch for that) Just nitpicking. (Dunno, if that changes anything of your statement.) -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________
Thomas Schilling <tjs_ng@yahoo.de> writes:
Pascal J.Bourguignon wrote:
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP).
No, not necessarily in all lisp impls. (e.g. AFAIK Allegro has a switch for that)
Just nitpicking. (Dunno, if that changes anything of your statement.)
if it does i'd still prefer case INsensitive completion. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
On Thu, Jul 01, 2004 at 12:32:29AM +0200, Thomas Schilling wrote:
Pascal J.Bourguignon wrote:
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP).
No, not necessarily in all lisp impls. (e.g. AFAIK Allegro has a switch for that)
Modern mode Allegro is not ANSI Common Lisp.
Just nitpicking. (Dunno, if that changes anything of your statement.)
Me too. :) -bcd -- *** Brian Downing <bdowning at lavos dot net>
On Thu, 1 Jul 2004, Thomas Schilling wrote:
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a
No, not necessarily in all lisp impls. (e.g. AFAIK Allegro has a switch
In all _conforming_ implementations. ;-) Cheers, -- Nikodemus "Not as clumsy or random as a C++ or Java. An elegant weapon for a more civilized time."
Thomas Schilling writes:
Pascal J.Bourguignon wrote:
Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP).
No, not necessarily in all lisp impls. (e.g. AFAIK Allegro has a switch for that)
Just nitpicking. (Dunno, if that changes anything of your statement.)
Note the difference between what I write and what you write: Symbols in COMMON-LISP are all in upper case. Not necessarily in all LISP IMPLS. In COMMON-LISP, all the symbols exported by the COMMON-LISP package are in upper case, as indicated by the last paragraph of: http://www.lispworks.com/reference/HyperSpec/Body/01_dada.htm If an given implementation choose to add an option to diverge from conformance, it's its problem. -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein
participants (5)
-
Brian Downing -
Marco Baringer -
Nikodemus Siivola -
Pascal J.Bourguignon -
Thomas Schilling