Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
This looks to me to be an example of believing that a fundamental issue can be fixed by renaming what you are doing.

It doesn't work like that.

The effect that you are trying to achieve is that of a global. If you succeed in achieving that effect, you will have all of the fundamental design advantages and disadvantages that globals have. (They do have both.) The mechanism that you use to achieve the effect has no relevance beyond the fact that you are imposing overhead and obscuring what you are doing.

This is why I recommend that people not just understand that something is bad, but also understand why it is bad. We tend to complain of "cargo cult" code where people borrow code by rote without understanding. But the flip side of the same coin is no better in the end, accepting that certain labels are bad without understanding why.

Therefore, unless you want a specific subtly different effect than what globals give, I would be honest about it and just declare a global with vars. Oh, every alternative will have small advantages and disadvantages over this. For instance using a single global hash gives you only "one" global - but you impose overhead and lose typo checking.

For more on the issues with globals, and how changing the label does (not) address them, see Pass by reference vs globals.


In reply to Re (tilly) 1: using strict and functions by tilly
in thread using strict and functions by idunno

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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2024-03-28 15:15 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found