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.
  • A child can't muck with a higher-level process's environment. It's part of the joy of unix!

    Having sequential siblings mess with environment is usually something like:

    in script0:
      eval `script1`
      eval `script2`

    script1 prints out bash commands like "export FOO=bar" which the running then evaluates into its own environment, leaving it there for script2 to see.

    In brief: the environment is not a good way for children to perform IPC.
    --
    rjbs
  • Module::Build has a feature that helps with this, the notes() method. You can get the Module::Build object inside your tests. This is really handy.
    • That does look handy... thanks!

      I just really wish I'd started with this (and the tests!!) two years ago when I started writing the modules!!

      The customer wants some pretty significant changes and I've convinced them that we need some tests to insure that the functionality doesn't degrade with all of the changes... so... I'm basically backporting tests into the system while trying to provide new features.

      And, the new features are needed soon (of course).

      Yuck.

      (OK... enough complaining. Back to work.)

      Agai