Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

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

Whatís your favourite way to make perl dump core or panic?

The Perl interpreter is quite good at doing the right thing when you give it sensible code, but it's easy to make it crash if you actually try to confuse it. That's a bit of a shame, but for the things that Perl tends to be used for it doesn't really matter that much.

Here are three of my favourites to get you started:

perl -e 'undef %:: or die' perl -e '()= sort {*a=*b, 1} 2,3' perl -e '@a=(1..5); map {@a=() if $x++>2, $_} @a'

All these are still broken in bleadperl, though the last now panics instead of dumping core.

This isnít wholly frivolous, because it would be useful to have a list of these bugs; though I don't want that to detract from the simple fun of trying to make something break.

Edit: g0n Moved to Meditations from SoPW

In reply to How to kill perl? by robin

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.