Re^2: Syntax highlighting for CPAN

[LanX]

Thank you, ...

...but do you know why it's necessary to use yet another syntax parser for Perl?

The quality is below perltidy -html (i.e. w/o reformating), e.g. if you look at the bottom of CGI.pm you will see the hash key -values highlighted.³

Thats not much better than the pure JS solution that Corion already proposed for perlmonksı, which could easily be adopted for CPAN and automated using scriptmonkey.

Talking about automation, I couldn't find an option to save highlighting as default (e.g. in cookie).²

Sorry if I may sound overly negative, I really appreciate the effort!

It's just my mentality to ask for insight and discuss other solutions.

1) see Free Nodelet hack: Syntax colouring

2) Hmm the setting is supposed to be stored automatically in a cookie, but I have problems to make this work in my FF.

3) seems like I misinterpreted the mechanism, looks like another pure client-side JS solution for highlighting. My Idea was rather to use perltidy for adding highlight-<span>s on the server side, and to control the CSS settings via JS on the client side. Should be much faster, too.

[DStaal]

As for reasons why to use yet another parser, it might have something to do with wanting to parse code snippets, which may not even be complete valid Perl, and which are embedded in other text.

Most of the parsers I know tend to assume what you feed to them is supposed to be valid code, and is all supposed to be code.

[LanX]

Good point, but IMHO perltidy is quite tolerant, I once spoke to a PHP haker who used it (well he had to care about regexing the comment symbols)

IMHO false positives with keyword based highlighting is so distracting, that it's rapidly switched off.

But maybe it's just me...

[Your Mother]

Talking about automation, I couldn't find an option to save highlighting as default (e.g. in cookie).²

It did save the highlighting for me; though I notice that /js/jquery-cookie.js is 404ing.