use Perl

• A few disclaimers are necessary there... (Score:2)

  by merlyn (47)

  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
  • Re:A few disclaimers are necessary there... (Score:1)

    by sheriff_p (1577) on 2005.07.11 5:31 (#41778) Journal

    Randal, Why are you so overwhelmingly negative about this project? It looks a bit petulant. +Pete

    Reply to This

    Parent

    • Re:A few disclaimers are necessary there... (Score:2)

      by merlyn (47)

      Why are you so overwhelmingly negative about this project?

      I'm only negative to the point that the hype needs to be spin-corrected.

      When Adam presents a fair and balanced description of PPI, I've been quiet. But when he presents an offsetting view, I present a counter-offsetting view.

      It's about awareness. Not everyone knows why only perl can truly parse Perl, so they see PPI and get big googly eyes, when in fact it's not what it advertises itself to be, until you read all the fine print. When Adam

      --
      

      • Randal L. Schwartz
      • Stonehenge
    • Re:A few disclaimers are necessary there... (Score:1)

      by Alias (5735)

      Well, except that perl can't parse Perl either.
      
      This is no Perl.
      
      (But more on that at the OSCON talk) :)