Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Update: Darn - it's back. Completely ignore the below meditation, instead to post a question!

This is a rehash of a stack-overflow answer I just made. I hope that's not against modern Perlmonks etiquette!

I recently got an odd error in some code that definitely worked before:

Can't upgrade BIND (1) to 9 at line 999

Google told me only that someone had seen the same error in a cgi once.

How I fixed it might be instructive although I'm still not exactly sure what it means. The code, that worked in some calling circumstances but not others, was a simple method forwarding method that looked a little like this:

sub quick_method { return shift->SUPER::some_other_method(@_); }

It's a little lazy, sure, but according to perl's left to right evaluation, it should (and usually was) the equivalent of this:

sub quick_method { my $self = shift; my @args = @_; return $self->SUPER::some_other_method(@args); }

I'm guessing that since @_ is, under some circumstances, a special way of accessing the stack and, under other circumstances, a fairly regular global list, the way in which the method was called was hitting different code paths.

Moral of the story - don't get too cute about modifying and using @_ in the same line of code!

In reply to Don't get too cute about modifying and using @_ in the same line of code by aufflick

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?

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

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (5)
As of 2023-12-03 13:48 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (20 votes). Check out past polls.