DeusVult wrote:
Now, with strict, this isn't really a problem, since it can be harmlessly yanked out once the code is no longer being developed.
I disagree for two reasons:
- No code is ever "finished".
- Can you prove to me that you've thoroughly unit tested your code to the point where "use strict" won't cause any issues?
I don't think the second point is that serious as most code
should go through significant unit testing, which will catch most
strict issues. The first point, though, is serious. Someone comes along to add a new feature, adds thirty lines of code only to fail to notice that "next_field" was spelled "next_feild". A two-second bug catch takes half an hour. Worse, if they don't catch it, they might code around it. Other programmers might come by and not appreciate the virtues of strict. Or maybe they assume the code is not strict compliant and don't bother trying. Why take it out? It's just begging for trouble.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.