I had two objections. First, I was mapping my concept blockless of postfix conditional onto postfix loops. Postfix loops' implementation is to create a block context. This was contrary to my experience with conditionals and I had to peek at some perlguts to realize this. My other concern was the debugging tools built into perl tell me that the next() was a static "goto" into a nonsensical location and was equivalent to not executing the next at all. It turns out the static "goto" information built into next is not used - it does its "goto" behind the scenes and in a place the debugging tools know nothing of. This exposes two perl bugs. One in the core is to populate this nonsensical op_next data and the other is in B::Concise where it reports the nonsense data. Here's a simpler implementation to show off the bug. push @out, $_ || next for @in;
-
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.
|