Databases
StackOverflow2013
Postsdbo
POHow can I pass common arguments to Perl modules?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I pass common arguments to Perl modules?
    primarykey
    data
    text
    <p>I'm not thrilled with the argument-passing architecture I'm evolving for the (many) Perl scripts that have been developed for some scripts that call various Hadoop MapReduce jobs.</p> <p>There are currently 8 scripts (of the form run_something.pl) that are run from cron. (And more on the way ... we expect anywhere from 1 to 3 more for every function we add to hadoop.) Each of these have about 6 identical command-line parameters, and a couple command line parameters that are similar, all specified with Euclid.</p> <p>The implementations are in a dozen .pm modules. Some of which are common, and others of which are unique....</p> <p>Currently I'm passing the args globally to each module ...</p> <p>Inside run_something.pl I have:</p> <pre><code>set_common_args (%ARGV); set_something_args (%ARGV); </code></pre> <p>And inside Something.pm I have</p> <p>sub set_something_args { (%MYARGS) =@_; }</p> <p>So then I can do </p> <pre><code>if ( $MYARGS{'--needs_more_beer'} ) { $beer++; } </code></pre> <p>I'm seeing that I'm probably going to have additional "common" files that I'll want to pass args to, so I'll have three or four set_xxx_args calls at the top of each run_something.pl, and it just doesn't seem too elegant.</p> <p>On the other hand, it beats passing the whole stupid argument array down the call chain, and choosing and passing individual elements down the call chain is (a) too much work (b) error-prone (c) doesn't buy much.</p> <p>In lots of ways what I'm doing is just object-oriented design without the object-oriented language trappings, and it looks uglier without said trappings, but nonetheless ...</p> <p>Anyone have thoughts or ideas?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbrian d foy
    1. USLeonard
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow can I pass common arguments to Perl modules?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow can I pass common arguments to Perl modules?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow can I pass common arguments to Perl modules?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload