I used to use this module until I started to get nonsense fail reports related to \r\n line endings. I've finally got rid of this module from all of my distributions and I don't suggest anyone to use this. I see that \r\n is *still* a problem after all these years: rt.cpan.org/Public/Bug/Display.html?i...
Brilliant :) I've wanted to write something like that myself, but never had the time. This module aims to compare the most re-invented wheel of CPAN: The template engines. Although it's near version 1.0, it needs some polishing (hence the 4 stars).
This module does not create constants but injects weird subs into your package that gains value after first call. Code itself is implemented with several goto()s and seems to be highly error prone. Also the distro reached v2 in a month. Wow!. If you need such a thing implement them as functions or object methods instead. There is a reason calling something a "constant". Stay away.
[Update] Reply To Aristotle Pagaltzis: Do not assume anything about a person you don't even know and read the both sources to see what they are doing.
In reply to Dan Dascalescu: you seem to be spamming CPAN Ratings. While I agree on some of your ratings, most are biased. It's usually a "best practice" to use the pure perl version as the default fall back. You can try the ::XS first, but it won't hurt to have a compatibility layer, if you are not configuring all the machines that the code runs.
And I don't think anyone cares if Catalyst used this or that. YAML is not part of Catalyst.
Nice module. Simple interface but no updates for 7+ years and the version number is 0.04 and has this rather long TODO list. Seems to work ok with latin languages but not so sure about the performance/correctness with chinese, japanese or arabic. There seems to be converters for ZH/JP at least but this wheel is not yet re-invented as a whole as it seems :)
Ignore the troll below (or above, depending on the number of edits the troll make) and just RTFM. The correct argument to pass a document encoding to CGI::header() is the "-charset" parameter.
See the "-utf8" pragma to enable auto-utf8 on input parameters.
Use a template module (Template Toolkit for example) for HTML generation not CGI.pm' s template interface.
Jonathan Rockway' s review does not make any sense either. You can still use CGI.pm for input processing and uploads and it is suitable for simple applications. Also it is still maintained and new fetures added if needed and stable.
Edit: It looks like the troll (BKB) is coward enough to not mention his/her edit and replaced the old one completely with a more nonsense review.
I was thinking about generating a local copy of CPAN and searched for how to do it and it turned out that all is needed is this module & app :) Very nice and useful. All you need is a .minicpanrc for configuration and then just execute `minicpan`
Reached v7 but no documentation and bad interface (no interface?). Alot of weird functions named as makafoo, makabar, etc. Reading the code just gave me a headache, but it's also like a time travel to see some prehistoric (released in 2008!) & bad coding style :p
Something usable at last! Leaky variables are a nightmare and they are too hard to detect inside large code bases. This module gives you precious information. But if the information list is too long, command line is not good for reading. Maybe printing to STDOUT can solve this problem. Also, some global variables from other modules are marked as leaky (like some DBI globals) this seems to pollute the information list. An option to disable certain packages can be good.
Nice. But there is a performance problem. Kate.pm loads all sub modules at once and this decreases performance and increases exec time. We can not use individual modules (::Perl.pm) for highlighting, since the highlightText() method is inside Kate.pm
I think that all methods must be moved inside another module (like Syntax::Highlight::Engine::Kate::Base) and all sub modules must inherit from this. And Syntax::Highlight::Engine::Kate must be just remain as a wrapper. Here is a little benchmark I did:
Weirdo :p And a method name like "foo" in the API?? This seems to be a private/personal lib that has little use to others. Code uses DBI internally, but the interface is bad and hard to understand (from my point of view).
Seems unnecessary as Geoff Simmons stated. It also uses " " named entity, which can create problems with XHTML (with the correct content-type header). Only few "named entities" are pre-defined in XML. One must use " " with XHTML docs or define nbsp manually in DTD (i.e. <!ENTITY nbsp " ">).
Anyway, there is no documentation in this module and the interface is not perlish, also the examples in the distro do not work on my system because of the usage of "glpOpenWindow" (I learned that from "J-L Morel"s page -- I do not know if it can be replaced with another function?) that's why I gave it a "2".