Re: Command Languages Versus Programming Languages

On Thu, 10 Oct 2024 17:55:32 +0100
Rainer Weikusat <rweikusat@talktalk.net> boring babbled:

Muttley@DastartdlyHQ.org ignorantly rambled:

On Thu, 10 Oct 2024 16:09:49 +0100
Rainer Weikusat <rweikusat@talktalk.net> boring babbled:

Muttley@DastartdlyHQ.org writes:

Its syntax is also a horrific mess.

>
Which means precisely what?

>
Far too much pointless punctuation. An interpreter shouldn't need the vartype

>

signified by $ or @ once its defined, it should already know.

>
For the purpose of variable declaration, how's the interpeter going to

Which part of "once its defined" did you not understand?

convenient, because the same name can be reused for a variable of a
different type, eg:
>
my ($data, @data, %data);
>
$data = rand(128);
@data = ($data, $data + 1);
%data = map { $_, 15 } @data;

What a mess. And I didn't realise perl allowed variables of different types
to have the same name! Insanity! Another reason never to use it again.

it's also convenient to type and easy to read due to being concise.

If you say so. Others may disagree.

and returns the next line read from this file handle. In list context,
it returns all lines in the file.
>
Eg, this a poor man's implementation of cat:
>
perl -e 'open($fh, $_) and print <$fh> for @ARGV'

Meanwhile in awk: { print }

Please don't enumerate everything else on this planet you also don't
really understand as that's probably going to become a huge list. ;-)

I understand Perl vies with C++ as the most syntactically messy language
in common use. Unfortunately I have to use the latter, I don't have to use
the former.