Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.

Re: How to kill perl?

by Perl Mouse (Chaplain)
on Nov 07, 2005 at 10:16 UTC ( [id://506270] : note . print w/replies, xml ) Need Help??

in reply to How to kill perl?

Kill Perl Golf:
$ perl -e '/(?{<})/' panic: top_env
If you swap the less then sign, it's just a syntax error:
$ perl -e '/(?{>})/' syntax error at (re_eval 1) line 1, near ">" Compilation failed in regexp at -e line 1.
(Reason: anything that might be the start of a quoted construct inside (?{}), but isn't followed by one panics perl. (?{'}), (?{"}), (?{`}), (?{<}), (?{/}), (?{?}), (?{q}), (?{m}) and (?{s}) all panic perl. Other single charactes seem to do ok (although I didn't check all of them).
Perl --((8:>*

Replies are listed 'Best First'.
Re^2: How to kill perl?
by robin (Chaplain) on Nov 07, 2005 at 10:58 UTC
      I was searching on "panic top_env" and came across this thread...

      Did you quote the right bug? Or did it's link change?

      The link you gave (now) points to a bug about array slice problems.

      Quantum Mechanics: The dreams stuff is made of