Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • So where's your patch which enables future users to share in your new-found knowledge without having to dig through google and blog-entries? Sometimes one doesn't have the time or energy to "give back", but surely the time spent writing this post would have been better spent creating such a patch?

    Sorry, don't mean to be too hard on you, but it always rankles when someone complains about a problem in a piece of OS software which they clearly know how to fix but instead of fixing it they write up their complaint and spew it forth onto the intertubes.

    • Heh, you're 100% right in theory, a little less in practice. The documentation for Image::Magick isn't the usual POD we all love: if you just do perldoc Image::Magick you'll get a couple of screens that redirect you towards the online docs [imagemagick.org]. Figuring out how to "send a patch" for those docs goes well beyond the effort of writing a post here. Call it lazyness :)

      There's more, in my opinion. The fact itself of calling such a parameter "magick" is questionable, because it doesn't make it immediately clear what