In the "olden days" of structuring program code, the standard for placing
"paragraphs" or routines within code was to place the "called" routine
below the routine which calls it (if possible).
Now I know I'm dating myself, but I see most of the "called" routines placed above the calling routines in the bulk of these modules...
Example - in shippling_lib.pl
sub calc_SBW is defined above
define_shipping_logic, which calls it
I'm sure it doesn't matter from a performance standpoint, but since Perl is
not a "compile, link & go" language, is there something about Perl that insists a routine be defined above, so it's interpreted efore the command that executes it?
Just an old dog trying to learn some new tricks...
Jim in Pittsburgh
(Could you tell I'm an old Fortran/COBOL guy?)
