Re: Command Languages Versus Programming Languages

On 30.03.2024 08:47, Stefan Ram wrote:

 
  But look at Pascal, Java, or Python. They are usually compiled
  into an intermediate code (called "p-code" in the case of
  Pascal) which is then interpreted (the interpreter is called
  "JVM" in the case of Java). Yet, we think of Pascal and Java
  as programming languages and of Python as a scripting language.

I never used an interpreted Pascal, nor one that produced p-code.
(As far as memory serves it was the UCSD Pascal dialect that
decided to use intermediate code to be interpreted.) My Pascal
programs have always been compiled.

And there were BASIC compilers on mainframes before the BASIC
interpreters on PCs became popular and widespread.

It's _the same_ language (modulo dialects), and languages are
usually defined by their grammar and semantics and not whether
it is interpreted/compiled or how it is run (VM or else).

I think it's obvious that interpretation vs. compilation or any
intermediate interpreted p-code is not an appropriate criterion
to declare something as a "scripting" language. You can't tell
whether a language, Pascal, BASIC, or any other language, is a
"scripting" language by that criterion. It's also generally a
fuzzy term; literature speaks vaguely about "typical" criteria
but cannot pin them down. - And that term isn't even helpful in
any way! - So why use it at all or religiously dispute about it.

Janis

 
  But this is actually an implementation detail: Java also can
  be compiled into machine code.
 
  [...]