Thank you all for your comments!
Because I am used to C/C++ I do not 'like' the usage of variables and
subroutines before even declaration in a source code 'instinctively'.
This is, of course, my personal spleen which may change with more
experience in using Perl.
brian d foy wrote:
>
> perl c
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
> 1. In my simple mind this would only make the interpreter jump through
> the script which should not enhance the performance.
perl compiles the script, then runs the intermediate digested form
of the human readable code.
> 2. Human bein
> -Original Message-
> From: "Stephan Tinnemeyer"<[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Thu Sep 20 06:22:29 PDT 2001
> Subject: structure of scripts (newbie Q)
>
> >I hope I did not overread this in the FAQ:
> >
> >In some
n Tinnemeyer"<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Thu Sep 20 06:22:29 PDT 2001
Subject: structure of scripts (newbie Q)
>I hope I did not overread this in the FAQ:
>
>In some tutorials I found the recommendation to put the code for
>subroutines at the end of
o create a
functional module.)
I, too, would be interested in other views on this subject.
- Roger -
- Original Message -
From: "Stephan Tinnemeyer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 20, 2001 2:22 PM
Subject: structure of scripts
I hope I did not overread this in the FAQ:
In some tutorials I found the recommendation to put the code for
subroutines at the end of a script (i. e. after calling them) but it was
never explained why I should do so. I only see disadvantages:
1. In my simple mind this would only make the interpr
