Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I would characterize a subroutine as a self-contained set of operations, performed on the arguments passed to it. opendirs sets the variable filehandle specified in the first argument, setting it to access the file system directory specified in the second argmument. unlink removes the file specified in its argument. rand(2) does something, and rand(100) does something similar but different, dependent on the different arguments. In particular, routines should be testable in isolation or in small groups.

So while you're doing well to use subroutines, if they are dependent on global variables then you're really writing one global, interconnected set of code. Addmittedly, in certain circumstances you may have global configuration variables, our $PI=3.14; or our $DEFAULT_SEPARATOR = ','; but that's a slightly different case .... but do try to avoid even those if you can.

As far as the list assignment:

my ($user, $lib) = qw(/home/john /lib);
is concerned, it works perfectly well:
my ($user, $lib) = qw(/home/john /lib); + print "\$user is '$user'.\n"; print "\$lib is '$lib'.\n"; # # Generates the output: # $user is '/home/john'. $lib is '/lib'.

--
TTTATCGGTCGTTATATAGATGTTTGCA


In reply to Re: using a subroutine by TomDLux
in thread using a subroutine by xjlittle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.