Re: Command Languages Versus Programming Languages

On 2024-03-29, 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
language" as a DSL designed for directing the actions of the operating
system makes much more sense, IMHO.

Common Lisp requires the implementation to be able to read
and execute printed expressions, without having them placed into
a file that must be translated to a compiled file.

The most prominent CL implementations compile every form before
executing it, even at the interactive prompt. It's invisible to the
user.

Scripting doesn't mean that the commands cannot be transparently
translated into antoher language before being executed.

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca