On 11/19/2010 9:22 AM, Martin Gregorie wrote:
[...]
> Indeed,
> it doesn't make sense there since executables are limited to .BAR or .CMD
> files, which are directly interpreted by the command processor, and .EXE
> or .COM files, which must be compiled before they can be run. AFAIK
> there's no
Am 19.11.2010 15:22, schrieb Martin Gregorie:
On Fri, 19 Nov 2010 01:43:28 +0100, Alexander Kapps wrote:
What difference does it make? Is 'print "Hello"' a program or a script?
Are you saying, that it depends on whether you have to manually call
some compiler?
Thats the way the term 'script'
On Fri, 19 Nov 2010 01:43:28 +0100, Alexander Kapps wrote:
> What difference does it make? Is 'print "Hello"' a program or a script?
> Are you saying, that it depends on whether you have to manually call
> some compiler?
Thats the way the term 'script' is usually used in the UNIX/Linux world.
I
On Fri, 19 Nov 2010 00:26:41 +, MRAB wrote:
> On 19/11/2010 00:07, Steven D'Aprano wrote:
>> On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
>>
>>> I use 'script' to refer to programs written in languages that don't
>>> have a separate compile phase which must be run before the prog
On 11/18/2010 7:57 PM, Martin Gregorie wrote:
[...]
> .pyc files are an optional extra: in a *nix environment they are not
> produced if you use a hash-bang line to execute the source file: they
> only appear if you run the source with a "python file.py" command.
>
Close, but no cigar. They are
On 11/18/2010 9:05 PM, Mark Wooding wrote:
Maybe, once upon a time, there was a meaningful distinction to be made
between purely interpreted languages and purely compiled languages.
No, there never was; only between interpreting and compiling
implementations.
Right. I remember using a C *int
Steven D'Aprano writes:
> On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
>
> > I use 'script' to refer to programs written in languages that don't have
> > a separate compile phase which must be run before the program can be
> > executed. IOW Python and Perl programs are scripts aloin
On Fri, 19 Nov 2010 00:07:05 +, Steven D'Aprano wrote:
> On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
>
>> I use 'script' to refer to programs written in languages that don't
>> have a separate compile phase which must be run before the program can
>> be executed. IOW Python and
On 19.11.2010 01:26, MRAB wrote:
On 19/11/2010 00:07, Steven D'Aprano wrote:
On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
I use 'script' to refer to programs written in languages that don't have
a separate compile phase which must be run before the program can be
executed. IOW Py
On 19/11/2010 00:07, Steven D'Aprano wrote:
On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
I use 'script' to refer to programs written in languages that don't have
a separate compile phase which must be run before the program can be
executed. IOW Python and Perl programs are scripts
On Thu, 18 Nov 2010 14:21:47 +, Martin Gregorie wrote:
> I use 'script' to refer to programs written in languages that don't have
> a separate compile phase which must be run before the program can be
> executed. IOW Python and Perl programs are scripts aloing with programs
> written as awk, J
On Thu, 18 Nov 2010 15:41:51 +, Grant Edwards wrote:
> On 2010-11-18, Martin Gregorie wrote:
>> On Thu, 18 Nov 2010 01:16:34 +, MRAB wrote:
>>
>>> I'd probably say that a "script" is a program which is normally not
>>> interactive: you just set it up, start it, and let it do its work (a
>
On 2010-11-18, Martin Gregorie wrote:
> On Thu, 18 Nov 2010 01:16:34 +, MRAB wrote:
>
>> I'd probably say that a "script" is a program which is normally not
>> interactive: you just set it up, start it, and let it do its work (a
>> "batch script", for example). It's also written in a language
On Thu, 18 Nov 2010 01:16:34 +, MRAB wrote:
> I'd probably say that a "script" is a program which is normally not
> interactive: you just set it up, start it, and let it do its work (a
> "batch script", for example). It's also written in a language primarily
> designed for convenience rather t
On 18/11/2010 00:28, Ben Finney wrote:
Alexander Kapps writes:
On 17.11.2010 19:38, Boštjan Mejak wrote:
What is the difference between a program, an application, and
software?
Alexander's guide is good. Some notes from a native speaker of English:
Program: A sequence of one or more instr
On 11/17/2010 05:10 PM, Alexander Kapps wrote:
On 17.11.2010 19:38, Boštjan Mejak wrote:
What is the difference between a program, an application, and software?
Software: The parts of a computer that you *can't* kick.
Programmer: the part that usually gets kicked...
-tkc
--
http://mail.p
Alexander Kapps writes:
> Application: Usually a large(er), complex program
I'd say that an `application' is specifically a program intended for
direct human use. Other things are servers, daemons and utilities. But
I might just be weird.
-- [mdw]
--
http://mail.python.org/mailman/listinfo/p
Alexander Kapps writes:
> On 17.11.2010 19:38, Boštjan Mejak wrote:
> > What is the difference between a program, an application, and
> > software?
Alexander's guide is good. Some notes from a native speaker of English:
> Program: A sequence of one or more instructions (even 'print "hello"'
> i
On 17.11.2010 19:38, Boštjan Mejak wrote:
What is the difference between a program, an application, and software?
Program: A sequence of one or more instructions (even 'print
"hello"' is a valid Python program)
Application: Usually a large(er), complex program
Software: The parts of a compu
On Wed, Nov 17, 2010 at 10:38 AM, Boštjan Mejak wrote:
> What is the difference between a program, an application, and software?
(1) This has nothing at all to do with (wx)Python specifically.
(2) Did you try consulting Wikipedia?:
http://en.wikipedia.org/wiki/Computer_program
http://en.wikipedi
20 matches
Mail list logo
