Dennis Lee Bieber writes:
> On Fri, 10 Sep 2010 12:25:17 +0200, Giacomo Boffi
> declaimed the following in
> gmane.comp.python.general:
>
>> Lawrence D'Oliveiro writes:
>>
>> > In message <8662yfklzu@aiuole.stru.polimi.it>, Giacomo Boffi wrote:
>> >
>> >> Dennis Lee Bieber writes:
>> >>
In message <86wrqtsxo2@aiuole.stru.polimi.it>, Giacomo Boffi wrote:
> Lawrence D'Oliveiro writes:
>
>> In message <8662yfklzu@aiuole.stru.polimi.it>, Giacomo Boffi wrote:
>>
>>> no BLOCKDATA?
>>
>> I think you mean COMMON.
>
> i meant BLOCKDATA
BLOCKDATA is an initializer. The actual s
Lawrence D'Oliveiro writes:
> In message <8662yfklzu@aiuole.stru.polimi.it>, Giacomo Boffi wrote:
>
>> Dennis Lee Bieber writes:
>>
>>> FORTRAN just differentiates by having the main file start with
>>> PROGRAM random_name
>>> whereas subfiles are all either (or both)
>>> SUBROUTINE another
In message , Mel wrote:
> But historical COBOL didn't pass parameters anyway. You read
> your optional arguments from a file, or accepted a few from an input
> device.
I think it could also read from switches. As in front-panel on/off switches.
--
http://mail.python.org/mailman/listinfo/python-
In message <8662yfklzu@aiuole.stru.polimi.it>, Giacomo Boffi wrote:
> Dennis Lee Bieber writes:
>
>> FORTRAN just differentiates by having the main file start with
>> PROGRAM random_name
>> whereas subfiles are all either (or both)
>> SUBROUTINE another_name(args)
>> FUNCTION that_other_name
Dennis Lee Bieber writes:
> FORTRAN just differentiates by having the main file start with
> PROGRAM random_name
> whereas subfiles are all either (or both)
> SUBROUTINE another_name(args)
> FUNCTION that_other_name(args)
no BLOCKDATA?
--
http://m
Dennis Lee Bieber wrote:
> On Thu, 09 Sep 2010 12:38:04 +1200, Lawrence D'Oliveiro
> declaimed the following in
> gmane.comp.python.general:
>
>> In message , Hugo
>> Arts wrote:
>>
>> > sys.argv is a list of all arguments from the command line ...
>>
>> Interesting that Python didnt bother t
On Wed, 08 Sep 2010 21:58:49 -0700, Dennis Lee Bieber wrote:
> On Thu, 09 Sep 2010 12:38:04 +1200, Lawrence D'Oliveiro
> declaimed the following in
> gmane.comp.python.general:
>
>> In message , Hugo
>> Arts wrote:
>>
>> > sys.argv is a list of all arguments from the command line ...
>>
>> Int
In message , Dennis Lee
Bieber wrote:
> None of them have command line arguments "passed" in to some
> starting point -- all had to use some runtime library function to ask
> for the command line contents.
It’s always a language-specific routine, since at the underlying POSIX level
(exposed by
On Thu, 09 Sep 2010 12:38:04 +1200, Lawrence D'Oliveiro wrote:
> In message , Hugo
> Arts wrote:
>
>> sys.argv is a list of all arguments from the command line ...
>
> Interesting that Python didn’t bother to mimic the underlying POSIX
> convention of passing the command line as arguments to the
On 9/8/10 7:38 PM, Lawrence D'Oliveiro wrote:
In message, Hugo Arts
wrote:
sys.argv is a list of all arguments from the command line ...
Interesting that Python didn’t bother to mimic the underlying POSIX
convention of passing the command line as arguments to the mainline routine.
There *is
In message , Hugo Arts
wrote:
> sys.argv is a list of all arguments from the command line ...
Interesting that Python didn’t bother to mimic the underlying POSIX
convention of passing the command line as arguments to the mainline routine.
I always felt it was more useful to have command argume
On 9/6/2010 11:48 AM, aug dawg wrote:
I've seen Python programs that can be activated from the command line.
For example:
hg
This displays a list of commands for the Mercurial revision control
system. But another command is this:
hg commit "This is a commit name"
Mercurial is written in P
On Mon, Sep 6, 2010 at 5:48 PM, aug dawg wrote:
> I've seen Python programs that can be activated from the command line. For
> example:
> hg
>
> This displays a list of commands for the Mercurial revision control system.
> But another command is this:
> hg commit "This is a commit name"
> Mercuria
14 matches
Mail list logo
