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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Performance/Behavior vs. PPI::HTML ? (Score:1)
Re: (Score:1)
The only problem is that, yes, PPI and therefore PPI::HTML are resource pigs. Parsing Perl is Hard
Personally, I use PPI::HTML when I can afford the CPU or I'm caching a lot, and the rest of the time I don't bother at all.
Re: (Score:1)
Well, perltidy is also quite big ... almost 1MB of source code!
If you have an ActiveState distrib, there is also the ActiveState::ScinePlex module which is quite good. I played with both ScinePlex and PPI while designing Pod::POM::Web, and found that the results are quite similar
Re: (Score:1)
That's mostly because it runs exceptionally evilly, from what I could tell reading it, it doesn't parse perl so much as nudge whitespace around.
And I believe it's actually a good deal faster.
And finally, PerlTidy doesn't actually do any syntax highlighting from what I understand, it just does the whitespace-shifting work, he'd have to be highlighting using something else.
Re:Performance/Behavior vs. PPI::HTML ? (Score:1)
Yes it does. In HTML mode it will spit out coloured code.
Reply to This
Parent