Re: Command Languages Versus Programming Languages

On Fr 29 Mär 2024 at 17:20, Muttley@dastardlyhq.com wrote:

On Fri, 29 Mar 2024 17:13:47 -0000 (UTC)
Kaz Kylheku <643-408-1753@kylheku.com> wrote:

On 2024-03-29, Muttley@dastardlyhq.com <Muttley@dastardlyhq.com> wrote:

On Fri, 29 Mar 2024 08:44:54 -0700
John Ames <commodorejohn@gmail.com> wrote:

On Fri, 29 Mar 2024 09:55:33 -0000 (UTC)
Muttley@dastardlyhq.com wrote:
>

My rule of thimb is that a scripting language is one whereby the
source code can be run immediately by the interpreter, eg perl,
python, regardless of what happens internally. A full fledged
programming language is one that requires a compile/debug/link step
first with the compiler and runtime (if required) being seperate. eg
Java, C

>
By *that* logic, even Lisp and Forth don't count as "full-fledged
programming languages" o_O Johanne's definition of a "scripting

>
As a counter point, good luck writing a device driver in lisp.

>
The Lisp machines had operating systems and device drivers written in
Lisp, interrupt-driven and all.  Where do you perceive the difficulty?

>
Were the mucky bits actually written in Lisp or was Lisp simply calling some
routines written in assembler? In the same sense that Python doesn't actually
"do" AI, its way too slow, the AI but is done in libraries written in C++ that
Python simply calls.

It was Lisp all the way down. Even the machine langauge was quite lispy
simply because the processor was a lisp chip.
Go read about it - there is lots of info about it on the net and if you
want, you can even run the lisp machines (several implementations) on an
emulator.

'Andreas
--
ceterum censeo redmondinem esse delendam