Re: Command Languages Versus Programming Languages

[ X-post list reduced ]

On 14.10.2024 16:47, Muttley@DastartdlyHQ.org wrote:

On Mon, 14 Oct 2024 13:38:04 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) boring babbled:

In article <veiki1$14g6h$1@dont-email.me>,  <Muttley@DastartdlyHQ.org> wrote:

On Sun, 13 Oct 2024 20:15:45 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) boring babbled:

Oh really?  Is that why they call it "machine language"?  It's
even in the dictionary with "machine code" as a synonymn:
https://www.merriam-webster.com/dictionary/machine%20language

>
Its not a programming language.

>
That's news to those people who have, and sometimes still do,
write programs in it.

 
Really? So if its a language you'll be able to understand this then:
 
0011101011010101010001110101010010110110001110010100101001010100
0101001010010010100101010111001010100110100111010101010101010101
0001110100011101010001001010110011100010101001110010100101100010

It's substantially (for me) not different from, e.g., Chinese text.

You need context information to understand it. But understanding a
language is not a condition for defining and handling a language.
If there's context information then people can associate semantical
meaning with it (and understand it).

To illustrate (just playing)...

  if then else then if or if and else end if

Are you able to understand that? On what abstraction level do you
understand it? Does it make [semantical] sense to you?
(Note: Using the proper translator and interpreter this is quite
dangerous code. For the puzzler; it's a coded shell fork-bomb.)

Janis