comment on

I'm an advocate of DRY, passing it around increases the error probability , e.g. typos.

OTOH globals tend to have a problem, if the line distance between creation and usage gets to big, or generally if scope and context are not easy to oversee.

I'd use a block scope to simulate an object˛, the "global" is used like a class-attribute.

{ 
  my $global="whatever";
  sub method1 { 
       ...;
       foo($global);
       ... 
     }
  sub method2 { 
       ...;
       bar($global);
       ... 
     }
  sub ...
}
[download]

Closures are in most simple cases more elegant than objects, especially in perlš!

(they just can't inherit, but that's not a "simple" case anymore).

Cheers Rolf

UPDATES:

(š) just compare to grandfathers lightweight object! No blessing, no $self ...

(˛) "encapsulation" to be more precise

In reply to Re: DBI, $dbh, and subroutines by LanX
in thread DBI, $dbh, and subroutines by jrsimmon

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.


Keep It Simple, Stupid
	PerlMonks