in reply to •Re: Re: Using a paramter value to call a module
in thread Using a paramter value to call a module

++, I'm in the unfortunate position of having to support and migrate some perlies that rely heavily on environment variables. Moving these into a production environment has been made more difficult than necessary by poorly implemented and documented code..
  • Comment on Re: •Re: Re: Using a paramter value to call a module

Replies are listed 'Best First'.
Re: Re: •Re: Re: Using a paramter value to call a module
by Brutha (Friar) on Feb 07, 2003 at 09:51 UTC
    Sorry, but do you really think, it would have been easier, if the values had been hard-coded?

    The problem is the documentation, not the use of environment variables. Depending on the amount, it could have been better to put them in a file instead of the environment, but that is a problem with the code, not the use of variables.

    --
    And it came to pass that in time the Great God Om spake unto Brutha, the Chosen One: "Psst!"
    (Terry Pratchett, Small Gods)

      yes and no.

      Yes it would have been easier if the design had been documented, however no, because the use of the ENV, (in this case) makes the code less portable, and more of a pita to set up on another host - which is independant of the documentation.

      I'm lazy, i like easy systems to install with minimal config changes.