What would be an argument against that behavior?
]]>2) Can the app be moved to a persistent environment where that argument is irrelevant?
If not, why not :-)?
3) Is it a case of premature optimization?
But at least the refs
stricture should stay on at all times. Turning it off in production means that your code is suddenly no longer safe from symbolic references if there is a bug that misinterprets user data.
In any case the overhead of strict
is negligible.
I actually leave warnings off in development as well, and turn it on in test scripts with
#!/usr/bin/perl
BEGIN {
$^W = 1;
}
What I was aiming for though is the contrast that no such case can be made for turning off strictures in production, and a strong case can in fact be made against turning off the refs
stricture in particular.
Now I need to figure out how to use the API to loop through all my repos and disable the issue tracker.
]]>