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.

Quit using FindBin 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Stealing a page from Schwern - have you filed a bug report?

    http://rt.cpan.org/Public/Dist/Display.html?Name=FindBin [cpan.org]

    • As I wrote in the comments of my other post about this [perl.org]:

      The whole point of FindBin is that if it can’t locate the script via $0 it will try to find it in the PATH […] Ripping that behaviour out 10 years after the fact doesn’t seem wise, even if the behaviour is broken for some edge cases. I’d prefer to deprecate FindBin in favour of a saner new alternative.

      • I read that, it doesn't change my position. You seem suprised that people are suprised FindBin is broken. Where is the bug supposed to be reported? In the designated place or some external forum.

        I think it is a bad precedence to suggest that we shouldn't document bugs because they have existed for a really long time and fixing them means deprecating the module entirely.

        I am not trying to be flippant or antagonistic. I just think it is unfair to expect folks to have read everything you have read.

        • I am entirely fine with a doc patch for FindBin, and if there is a better module, a deprecation notice in the FindBin docs pointing to it. That’s not “fixing” FindBin, and therefore is a good idea. I hadn’t thought of that.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.