Re: Command Languages Versus Programming Languages

On Sat, 30 Mar 2024 18:10:36 -0000 (UTC)
Kaz Kylheku <643-408-1753@kylheku.com> wrote:

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

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

>
So if I write:
>
int main()
{
system("ls | wc -l");
return 0;
}
>
Thats a script?

>
The "ls | wc -l" part is a script, passed off for execution to a
language that mainly supports scripting.

So its not a script.

Note the non-scripting features here like "int main",
which doesn't /do/ anything, and typically the need to compile
and link this in order to run it.

There may be plenty of surrounding code that does do something.

No? What if I use popen() or execve() then? Where do you
draw the line?

>
If you use popen and execve, you're using more systems programming
functional blocks that are not scripting commands.

They both call high level commands so is it scripting or programming?

I'm not being obtuse. There is no hard dividing line between scripts and

>
Right now you're doubling down on obtusity, by my estimate.

Perhaps you don't understand what being obtuse actually means.