On 2011.10.23 9:08 PM, Father Chrysostomos via RT wrote:
Show quoted text> This really has nothing to do with 5.13.7. 5.13.7 disabled some weird source
> filter behaviour (in that the filter enabled within a string eval would apply
> to whatever outer dynamic scope was being compiled). Either making use_ok work
> with pragmata *or* reenabling the source filter would fix the 20 or so modules
> affected. The latter is what happened, so 5.14.0 is no different from 5.12.0
> in that regard. So mentioning 5.13.7 at all in the changelog is misleading.
Filters seem to work with an unpatched Test::More and 5.14.1.
use warnings;
use Test::More;
BEGIN { use_ok "Semi::Semicolons"; }
pass()Peterbilt
done_testing;
Did that filter behavior change make it out of 5.13?
Show quoted text> use_ok has, as far as I know, never worked with pragmata.
D'oh! You're right! I wonder if it's worth starting now. Well, work's done.
I'll fix the change log.
Show quoted text> +Lexical effects will occur as usual. For example, this will turn on strictures.
> +
> + use_ok "strict";
>
> This would be better written as BEGIN { use_ok "strict"; }, because a simple
> use_ok "strict" won’t enable it for the current scope.
Got it. Done.
Show quoted text> You don’t like my coding style, but have you seen the perl source. :-)
Bonitas non est pessimis esse meliorem.
Show quoted text> I actually find more compact code easier to read, because I don’t have to
look so
Show quoted text> far to understand it.
Greatthenletsgetridoftheinterstitialspaceandparagraphs!
I presume you mean scrolling rather than physically turning your head and
eyeballs?
Less tongue in cheek... a large project cannot be fully understood at one
time. It is more important to find the piece you care about, and its scope of
effect, than to study code in detail. This is why code should be optimized
for skimming with the scope and structure laid bare. This is also why any
given scope should remain short. A narrow scope forgives many sins. The
blocks I've been using lately in my tests are a great example.
I have a talk on this, unfortunately there's no video, but here's the slides
with notes:
http://schwern.net/talks/Skimmable%20Code%20-%20OSCON%202008%20w:notes.pdf
That said, vertical whitespace is valuable. But rather than conserve it I
expand my store. I've got my editor spanning the full height of the screen
and using the smallest most compact font my poor eyes can easily deal with.
Helps to have a high resolution, widescreen laptop. :-)
BTW Inconsolata is a fantastic fixed width font. Gave me a lot more space
and clarity.
http://www.levien.com/type/myfonts/inconsolata.html
--
s7ank: i want to be one of those guys that types "s/j&jd//.^$ueu*///djsls/sm."
and it's a perl script that turns dog crap into gold.
RT for rt.cpan.org