Re: Command Languages Versus Programming Languages

Liste des GroupesRevenir à cl lisp 
Sujet : Re: Command Languages Versus Programming Languages
De : Muttley (at) *nospam* dastardlyhq.com
Groupes : comp.unix.shell comp.unix.programmer comp.lang.misc
Date : 29. Mar 2024, 19:20:49
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uu6t9h$dq4d$1@dont-email.me>
References : 1 2 3 4 5
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.


Date Sujet#  Auteur
20 Sep 24 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal