RE: RE: Perl Module evaluation mechanism

Actually XML::Simple is pretty good, and powerful enough for a wide category of problems.

Which shows that you would probably have been wrong here.

This is why I really think a place where users can report on modules, link to similar modules, write why they choose the module and so on would help tremendously.

Even indicating why you DIDN'T choose a module, or why, after evaluating it you rejected it would help authors to improve them.

Plus maintaining a module is quite a burden and if nobody uses it or if there is a better one out there the author can decide to give up on the module and notify users. I know of more than a couple of modules on CPAN that are not maintained and that will never be of much use for anybody. The problem is that they take up 2 lines in the directory listing, just like CGI.pm

Comment on RE: RE: Perl Module evaluation mechanism

Replies are listed 'Best First'.
RE: RE: RE: Perl Module evaluation mechanism by gaspodethewonderdog (Monk) on Aug 31, 2000 at 19:29 UTC
hehe... that's why I avoided commenting on XML in particular because I don't know ;). But from experience LWP::Simple and others have been... well simplified versions of the other versions. You could certainly build web spiders/robots with LWP::Simple, but there are a lot of conventions that aren't taken into account and you would have to implement yourself. A module 'accounting' repository would be great. It would be nice to know which modules are maintained and not... who used which for what reason... all that. Maybe the powers that be will decide to implement that feature some day :)	[reply]

Replies are listed 'Best First'.

RE: RE: RE: Perl Module evaluation mechanism
by gaspodethewonderdog (Monk) on Aug 31, 2000 at 19:29 UTC

But from experience LWP::Simple and others have been... well simplified versions of the other versions. You could certainly build web spiders/robots with LWP::Simple, but there are a lot of conventions that aren't taken into account and you would have to implement yourself.

A module 'accounting' repository would be great. It would be nice to know which modules are maintained and not... who used which for what reason... all that. Maybe the powers that be will decide to implement that feature some day :)

[reply]