Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Day 1313: PPI 1.000 released 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • 100% "Round Trip" safety

    ... provided you don't change the document in any way, like perhaps "strip comments" or anything that is not the NULL transformation.

    If you do any transformation, you will not know that you've misparsed. You'll simply get the wrong result, and you will damage code.

    Although it took a new definition of "parse", perl is now no longer the only thing that can parse Perl.

    I know you're hinting at it with your definition of "parse" caveat there, but I think it deserves a better

    --
    • Randal L. Schwartz
    • Stonehenge
    • I think the interesting question is whether a 98% solution is useful or useless. I'd say it's possible to do useful things with it. It's not like no-one knows Perl is dynamic.

      So let's not depend on PPI to tell if it got it wrong.

      If you're doing manual refactoring, do you have tests to back up your transformation? If you don't, you're doing it wrong. Same with using a PPI backed refactoring tool.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.