Differences between version 14 and previous revision of LISP.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 14 | Last edited on Thursday, November 20, 2003 11:20:06 pm | by StuartYeates | Revert |
| Older page: | version 13 | Last edited on Tuesday, November 11, 2003 5:27:28 pm | by AristotlePagaltzis | Revert |
@@ -1,11 +1,11 @@
The name is an [Acronym] for __Lis__t __P__rocessor.
It is the canonical FunctionalProgrammingLanguage. EdsgerWybeDijkstra [approves | http://www8.informatik.uni-erlangen.de/IMMD8/Services/SchemeTeach/Pages/ch1/sec3_42.html] of it.
-The secret
to reading
[LISP
] is to look at the indenting. You will go mad if you count
the brackets
.
+There was an attempt
to build lisp-oriented hardware devices known as
[LispMachine
]s. This failed, but it
is not clear whether it failed because it was an inherently worse way
to build hardware or whether it was just sufficiently different that it couldn't compete with conventional hardware because of
the economies of scale in design, manufacturing and integration
.
-The secret to writing [LISP] is to always use an editor such as [Emacs] that autoindents [LISP] code and highlights matching brackets for you.
+The secret to reading [LISP] is to look at the indenting. You will go mad if you count the brackets.
The secret to writing [LISP] is to always use an editor such as [Emacs] that autoindents [LISP] code and highlights matching brackets for you.
The name [LISP] has really come to denote a family of [ProgrammingLanguage]s in practice:
; [CommonLisp] : Standardised, heavy-duty Lisp - "the most thorough programming language in the universe".
