Re: Command Languages Versus Programming Languages

On 2024-03-30 22:28, Keith Thompson wrote:

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

On 2024-03-29 02:14, Lawrence D'Oliveiro wrote:

At one time, we distinguished between “scripting” languages and
“programming” languages. To begin with, the “scripting” languages were
somehow more limited in functionality than full-fledged “programming”
languages. Or they were slower, because they were interpreted.

[...]
>
The key difference is that a program in a scripting language need not
to be complete or known in order to be executed.
>
The limitations and ugliness of scripting languages is determined by
this requirement, but also easiness of use.

 Perl, Python, and Lua are all considered scripting languages, and for
all of them a syntax error at the end of a script will prevent any of it
from being executed.  The distinction is that they're not optimized for
interactive use, as shell languages are (though they all can be used
interactively).

I was not talking about [syntactically] incorrect incomplete programs. In a scripting language an incomplete program can be correct and executable. E.g. I type in bash:
    ls
This is only a part of my program. Because then I inspect the output and type:
    rm foo.bar
After that I turn off the computer. My program is complete now.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de