All the Perl that's Practical to Extract and Report
use Perl Log In
Alias (5735)
PPI 1.117 released. Perl::Critic hopefully now less broken
I've just uploaded PPI 1.117 to the CPAN.
This release contains a fixes for a number of things I broke in 1.116, but which did not have test cases (and so I didn't notice I had broken).
In particular, trivial compound statements should work again, so that something like...
LABEL: {
print "Hello World!";
}
As PPI's biggest "client" (by user count at least) I probably need to get into the habit of installing Perl::Critic on the new release to make sure it still works.
That said, Perl::Critic seems to still be broken with 1.117, but the failures don't look obvious, and so my hope is that the critic guys can release a new version shortly which adapts to the PPI changes/fixes, or that they'll commit more test cases I haven't covered.
Either way, I apologise for the short period of instability to Perl::Critic, hopefully we'll get this stuff cleaned up shortly.
because that's exactly how much difference there is. :-)
--Larry Wall in <10209@jpl-devvax.JPL.NASA.GOV>
Thanks (Score:1)
An anecdote: Perl parses "-t" aggressively. Consider the following code:
3-t(); # syntax error
3-test(); # Undefined subroutine &main::test
PPI doesn't treat the first case the same way Perl does, but it's a syntax error so does it really matter?
Re: (Score:1)
Perl's intepretation changes over time (each version has slight differences here and there). Witness how selfgol only works on a few particular versions of Perl.
PPI doesn't try to maintain bug for bug compatibility, because it simply can't. It has to be somewhat compatible with all versions.
So the general direction is that BOTH of $Perl{perl} and $Perl{PPI} trends towards $Perl{Larry}. On the way, $Perl{PPI} also tries to get as close as i
Re: (Score:1)
Re: (Score:1)