in reply to Re^2: System usage monitor
in thread System usage monitor

You should definitely have strict in production code, but I think warnings can be dropped after development.

Anyone care to back me up?

Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!

Replies are listed 'Best First'.
Re^4: System usage monitor
by gellyfish (Monsignor) on May 31, 2005 at 14:11 UTC

    To be honest if I was going to drop one of them from production code it would be strict - the circumstances that strict prevents from arising are unlikely to occur if the code is unchanged, whereas warnings may reveal unexpected problems with external data, as an example.

    /J\

[reply]
[d/l]
[select]

In Section Code Catacombs