Re: Command Languages Versus Programming Languages

Liste des GroupesRevenir à cu programmer 
Sujet : Re: Command Languages Versus Programming Languages
De : Muttley (at) *nospam* dastardlyhq.com
Groupes : comp.unix.shell comp.unix.programmer comp.lang.misc
Date : 29. Mar 2024, 19:18:23
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uu6t4v$dob8$1@dont-email.me>
References : 1 2 3 4 5
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.

Umm, no, try again.



Date Sujet#  Auteur
10 Nov 24 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal