| CPAN Ratings (Gamma) Ratings and Reviews for CPAN | |
| » Home « | Search | About | Login |
Find a distribution you would like to review:
To write a review you'll need a Bitcard account.
This module would be soooo nice and useful if it wouldn't break all filename globbing globally in other modules.
Therefore I strongly suggest moving this module below the Acme:: namespace where you can expect such things.
See bug
http://rt.cpan.org/Ticket/Display.html?id=27286
for some details.
*UPDATE:*
This issue is fixed with v0.0.5.
I therefore raised my overall rating. Thanks.
Steffen Schwigon - 2008-05-15 23:26:07
Was this review helpful to you?
Yes
No
Would love an example of using the shade shading object.
This is an incredible module, limited only by documentation so far.
cm1 - 2008-05-15 14:03:21
Was this review helpful to you?
Yes
No
Its a mistake to ignore SAX, DOM, XOM, StAX and all the rest of the well known idioms for xml processing ... though if u find yourself needing to work with mixed data (text and xml) or have a little XML language and what to write a processor for it ... XML::Descent is fine, quick and performant enough.
As I have worked with recdescent perl package I probably knew what I was looking for in this package; generally I found this to do what it says 'on the tin'.
Jim Fuller - 2008-05-15 08:17:44
Was this review helpful to you?
Yes
No
Although there is an external dependency of libssh2, I feel this module is much easier to use and much (much,much,...) easier to install then the alternatives Net::SSH or Net::SSH::Perl.
derby - 2008-05-15 04:03:02
Was this review helpful to you?
Yes
No
I like
Sergey Lepenkov - 2008-05-15 02:38:01
Was this review helpful to you?
Yes
No
Great module.
It takes care of a lot of the tedious code you have to write to use DBI. The method names needed to access the results are easy to remember, and it delegates very sensibly common tasks, like creating HTML tables from the results, to other modules.
I am not really into ORM, I prefer to write the SQL myself, and this is the best module I've found for this. Basically its interface is what DBI's should be (which of course is easier to figure out now than when DBI was written).
mirod - 2008-05-15 01:09:51
Was this review helpful to you?
Yes
No
BSD::Resource allowed me to go from nothing to being able to trap core dumps in a matter of a few minutes. With no external dependencies, installing BSD::Resource is a breeze, and only a quick skim of the documentation was needed to determine how to increase the resource limits I was after.
Thanks Jarrko. Two thumbs up.
Paul Fenwick - 2008-05-14 23:00:11
Was this review helpful to you?
Yes
No
While the documentation is a little brief, and the Create() call not returning the process object has thrown me a few times, Win32::Process provides a simple and straightforward way of starting a process under Windows.
Given that it comes bundled with the widely distributed ActiveState Perl, this makes Win32::Process an excellent choice for process manipulation which I regularly use in my own work.
Paul Fenwick - 2008-05-14 21:42:26
Was this review helpful to you?
Yes
No
Haven't used it yet, but ++ for using Continuity and ++ for porting Camping to Perl. Oh yeah, and ++ for the name too :)
Stevan Little - 2008-05-14 10:20:18
Was this review helpful to you?
Yes
No
5 start for a developer release of a module that does almost nothing (yet) because authors like Claes deserves to be rewarded by some admiration and coverage.
A Java Virtual Machine written in Perl is a cool thing in itself but the goals stated in the documentation make it even more interresting:
Implement multiple bytecode backend execution engines, such as:
* Simple switching runloop
* One that can transform Java bytecode to perl optrees directly
* Transform bytecode -> Perl source and eval
* Fast JIT:ing backend written in XS
Have a look at Claes other modules too, JavaScript, Parse::Java and Scripting come to mind.
نديم الخمير - 2008-05-13 16:24:11
Was this review helpful to you?
Yes
No
- Extremely bad name (for the little it does).
- Extremely bad namespace.
- Extremely bad documentation.
- Extremely bad to not use one of the already existing logging module or extend one.
نديم الخمير - 2008-05-13 16:10:00
Was this review helpful to you?
Yes
No
I really like it.
This module helps surviving in a multi-language work environment where you need to participate in the discussion about the typical Perl FUD. And, admittedly, it really adds even more beauty and readability to your code.
I used it in the context of a Moose'ified and RPC:XML::Server-based application, providing an IMHO sufficiently complex environment of subs and methods that finally gave me a good feeling about this module, not being that alpha grade as it calls itself.
I would, of course, really appreciate it if the trailing semicolon after a method can be avoided. But currently the advantages in readability are worth it.
Steffen Schwigon - 2008-05-13 08:13:31
Was this review helpful to you?
Yes
No
DBIx::Simple is sugar spread on DBI (it should really have been named DBI::Sweet). It's usage will make you code far more readable, quicker to write, and with a lot less boilerplate code.
This is my #1 choice for database management, as using the DBI directly requires some tedious coding which is senseless to do by hand.
DBIx::Simple, even though it does provide optional query abstraction through SQL::Abstract, does not feature database abstraction. For that you should take a look at more advanced modules such as DBIx::Class and Rose::DB::Object. However, for the quick and simple case, DBIx::Simple just rocks.
Michele Beltrame - 2008-05-12 01:39:25
Was this review helpful to you?
Yes
No
There are really occassions when you want the order preserved. Consider the following snippet for XML special character conversion. You can now say:
tie (%escape_symbols, Tie::IxHash,
qq (&) => '&',
qq (\042) => '"',
qq (>) => '>',
qq (<) => '<'
);
Imagine using these key,value pairs in a regex for substitution. Here the order is vital, as the & signs needs to be replaced first, otherwise your routine might clobber over the & symbols you use for the other replacements!
Neat and simple package, that does exactly what it says it will do.
Mark Kramer - 2008-05-11 12:00:45
Was this review helpful to you?
Yes
No
It seemed like a great package at the time, but I had to abandon it for several reasons, most of which have to do with lack of control.
It started when I wanted to add a <dc:creator> element. For that, you need to be able to declare extra namespaces in your <rss version ..> declaration, like xmlns:dc="http://purl.org/dc/elements/1.1/". This module gives you no control over that.
Then there's the whole CDATA issue. If you want your RSS feed to validate, you will going to have to be able to enclose portions of your content in CDATA tags (like, say, image links in an item's description element). XML:RSS has no support for any control over how to interpret/not to interpret your content: it just rigorously tries to escape/encode everything. An option to take in your content raw, like descriptionRAW =>, for instance, would have been needed to accommodate this need. But it's absent.
So, eventually, you'll wind up with an RSS feed that won't validate (unless you do something extremely 'plain' in your feed). It's ease of use is a plus: you whip out a feed in no time (even though the documentation really leaves to be desired). But, on the whole, this package offers not enough control to get things just right (right enough, at least, for you to generate feeds that will fully validate).
Mark Kramer - 2008-05-11 06:08:27
Was this review helpful to you?
Yes
No
A very handy way to add debugging to a program without having to use lots of print statements.
BKB - 2008-05-10 18:36:17
Was this review helpful to you?
Yes
No
The Changes file has traditionally been a *human*-readable file. The last thing somebody expects when reading a history file is to see YAML. Yuck!
If you want to have a machine-readable change history, use a different filename like "Changes.yml". And generate a human-readable file from that.
Additional mini-rant:
A machine-readable Changes file won't solve the problems that it's intended to. There's no guarantee that a change marked as "security fix" or "bug fix" won't break your system anyway by introducing new bugs or fixing ones that you thought were features, nor is there a guarantee that the author tagged changes correctly. And if a security fix is mixed in with API changes, then you can't separate the two.
If you're so concerned about updates breaking your system, then you're a fool to rely on automated tools in Perl. Read the Changes file, look at version diffs, test on a different server before upgrading. (This is what a responsible sysadmin should do anyway.)
Or better yet, don't upgrade if you don't have to.
Robert Rothenberg - 2008-05-09 12:07:18
Was this review helpful to you?
Yes
No
Excellent module. I've been using it in a file distribution system. Currently I'm now building a much larger multi-processing system that uses this module.
Richard Faasen - 2008-05-09 05:42:54
Was this review helpful to you?
Yes
No
Excellent module. I've been using it in a file distribution system. 'forks' works very nice in combination with Thread::Queue::Any.
Richard Faasen - 2008-05-09 05:40:38
Was this review helpful to you?
Yes
No
that all!
ares_yu - 2008-05-08 23:36:27
Was this review helpful to you?
Yes
No
It does what it says it does - what more could you want? Nice module with no fuss and no mess, has been very useful to me.
BKB - 2008-05-08 22:47:23
Was this review helpful to you?
Yes
No
First of all, the documentation of this module is difficult. The example doesn't work, it has ' in the wrong places, the "native_query" method used for searching isn't documented, and when you do get it to run it just prints out HASH(0x10239485) type of things.
Secondly, it doesn't seem to work properly - the results I got were nonsense, and I couldn't see what I was supposed to do from the documentation. I wanted to search by ISBN but it didn't make it clear how to do that.
In the end it was much easier to write the scraper "by hand" using LWP::Simple and the excellent API documentation of ISBNdb.com than using this module, so my advice is to forget it.
BKB - 2008-05-08 22:45:55
Was this review helpful to you?
Yes
No
I'm not sure why the reviews for this module are so negative. First of all, there is no requirement that you install, require, or use this module to have a machine-readable Changes file. You just write it, and this module processes it on the toolchain end.
The possibilities a machine-readable Changes file opens up are enormous. Have you ever installed YAML? You'll notice that it warns you that it is incompatible above 0.60 *every time you install it*. If the toolchain was aware of tags in the Changes file, then CPAN.pm could warn you, and you could set an "I don't care option". Or, you could set a "log whenever I upgrade something marked as incompatible". Then when your app breaks, you can review the log and see which module changed something. Or, you could simply refuse to install that module.
Finally, I had no trouble installing this module. "cpanp install Module::Changes" and there it was. I'm not sure what was wrong with the other reviewers' machines, but the problem is probably on their end.
Anyway, the other reviewers seem pretty clueless (about this module, and in general), so I would take their reviews with a very large grain of salt.
Jonathan Rockway - 2008-05-08 15:32:57
Was this review helpful to you?
Yes
No
Simple, flexible and blindingly fast code profiling system. Stupidly useful. Thoroughly recommended.
Adrian Howard - 2008-05-08 09:29:35
Was this review helpful to you?
Yes
No
Don't bother with this - it needs the drivers but most of them don't work any more. I needed to scrape some ISBNs so I tried this out, but I ended up writing a simple scraper "by hand" (i.e. get the page with LWP::Simple, then chop it up to get the data) without using this module.
The problem is that as the web page formats change with time, if nobody updates the drivers for each ISBN data site, then they can't be used any more. At the moment nobody seems to have maintained most of the drivers for three or four years, so best not to use this thing unless someone starts maintaining the drivers again.
BKB - 2008-05-08 06:21:15
Was this review helpful to you?
Yes
No
|
Perl.org sites
: bugs
| dev
| history
| jobs
| learn
| lists
| use
Site Information and Contacts |
|