http://www.perlmonks.org?node_id=373010


in reply to future warnings

How about making it a build-time config setting? Overridable by a use warnings parameter.

That way, people could specify that they don't want to see "just useful" warnings that didn't exist prior to some version. It wouldn't help those of us who use binary distributions, but we deserve what we get:)

It wouldn't be too onerous to add the version => 'x.x.x' to existing scripts that suddenly start bellyaching. I would imagine that most shops run a new distribution in a test environment for a while before upgrading production servers anyway?


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Replies are listed 'Best First'.
Re^2: future warnings
by dragonchild (Archbishop) on Jul 09, 2004 at 00:52 UTC
    What's a test environment?

    ------
    We are the carpenters and bricklayers of the Information Age.

    Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

    I shouldn't have to say this, but any code, unless otherwise stated, is untested

      That's where you change stuff in production and quickly put it back before anyone notices you broke it!

      Cheers,

      -- Dave :-)


      $q=[split+qr,,,q,~swmi,.$,],+s.$.Em~w^,,.,s,.,$&&$$q[pos],eg,print