For Perl up to and including 5.10, calling split in scalar or void context had the side-effect of setting @_.
This mis-feature was removed in Perl 5.12.
That was great news for most Perl programmers because this side-effect "feature" was unnecessary, an ugly wart.
It was sad news for golfers though because side-effects are frequently useful in golf.
In fact, I recently experienced a similar split annoyance in Compression in Golf: Part III, as described in the "Fun with split" section in that node.
Simply changing @_ to @z say should fix thospel's original solution at the cost of three strokes:
$_=$`.$_.$'.<>;@z=split//;${/[@z[map{$i-($i="@-")%9+$_,9*$_+$i%9,9*$_%
+26+$i-$i%27+$i%9-$i%3}0..8]]/o||do$0}for/0/||print..9
I expect you could do better than that, though I haven't tried.
-
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.
|
