Re: Command Languages Versus Programming Languages

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

On Fri, 29 Mar 2024 17:09:56 -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 11:40:03 +0000
Richard Kettlewell <invalid@invalid.invalid> wrote:

Muttley@dastardlyhq.com writes:

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

>
C can be a scripting language by that rule:

>
No definition is perfect in this case, its all shades of grey.

>
Yes, a definition can be close to perfet here:

>
Define perfect. Yours isn't.
>

Scripting is an activity, a use case, not a language.

>
So if I write a program to for example process some files in a directory by
your argument its a script whether I write it in shell, python, C++ or
assembler.

I also wrote: "Scripting refers to executing commands which are so high
level that they are entire applications or functional blocks within an
application."

If you write the program in assembler, are the instructions
"commands which are so high level that they are entire applications
or functional blocks within an application?"

In the assembly language program, mulitiple instructions, irrelevant
to the file processing task, are required just to correctly set up a
function call with parameters and return from it.

You're just being deliberately obtuse, not to mention snippy with the
scissors.

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