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.
  • I know this is far beyond your scope of emergency release, but I wonder about your diff. Why use

    $MAKE = $Config{make} eq 'dmake' ? 'dmake' : 'nmake';

    when you can just use

    $MAKE = $Config{make};

    $Config{make} is supposed to hold whatever is necessary to invoke whatever make program is there for the platform, so just trust it...

    • Because you want necesarily trust it all the time.

      In particular, if you are setting up activestate is only tells you what it was built with, not what you are running it with. So there are cases where it will lie. So I'm fairly careful to correct the case I know is ok (dmake).
      • > Because you want necesarily trust it all the time.

        That should read "Because you can't necessarily trust it all the time".

    • "What you're running with" is what Config.pm says. If you want the Perl tool suite to "run" a different make tool, adjust your Config.pm to match it. Relying on weirdo magic to counteract Config.pm leads to untraceable insanity.

      • > Relying on weirdo magic to counteract Config.pm leads to untraceable insanity.

        Of course, but I'll note that I didn't introduce the untraceable insanity.

        I've REMOVED it for one specific case I know works, and I'm otherwise carefully trying to avoid blatantly refactoring someone else's code I'm just a caretaker for.