Re: turn off strict for production code

I'd like to keep strict on for development and testing and then comment it out in the final code that we ship. Is there an easy way to do this without actually keeping different versions of the code?

One way is to just comment out the use strict when you check the code into your revision control system. That way, when you install onto your Production servers, use strict will be disabled. When you develop, uncomment the same line after you check it out from your version control system.

Having addressed your question, please check out this thread regarding using strict. Not using it can be compared to not wearing seat belts, not checking your chute before going skydiving, not wearing orange when hunting and not wearing a helmet when driving a motorcycle. I sure don't want to start a side thread based on those comparisons -- you already know that you should be using strict. You know that you should be doing testing. It's a philosophical thing -- figure out what you should be doing, then be that person.

Good luck.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Comment on Re: turn off strict for production code Select or Download Code

Replies are listed 'Best First'.
Re^2: turn off strict for production code by halley (Prior) on Sep 12, 2005 at 15:47 UTC
Never expect a developer to change the file's settings on checkin/checkout reliably. "Oh, what I'm doing is just such a quick change, I'll skip that." You might think that checkin/checkout hooks are the answer. Under that scheme, you make the version control system tweak the code on checkin/checkout for you. Example: checking out to a developer box means "use strict;" checking out to test servers means "use strict;" checking out to production servers means "no strict." Until you forget to add or remove certain usernames from a list. And don't forget the heisenbugs which somehow only show up when there's no debugger around. No, version control is not a part of the code. Version control is insurance against mistakes and disasters, but not a tool which actively tunes your applications. Just because it's possible doesn't mean it's a good practice. -- `[ e d @ h a l l e y . c c ]`	[reply]

Replies are listed 'Best First'.

Re^2: turn off strict for production code
by halley (Prior) on Sep 12, 2005 at 15:47 UTC

You might think that checkin/checkout hooks are the answer. Under that scheme, you make the version control system tweak the code on checkin/checkout for you. Example: checking out to a developer box means "use strict;" checking out to test servers means "use strict;" checking out to production servers means "no strict." Until you forget to add or remove certain usernames from a list. And don't forget the heisenbugs which somehow only show up when there's no debugger around.

No, version control is not a part of the code. Version control is insurance against mistakes and disasters, but not a tool which actively tunes your applications. Just because it's possible doesn't mean it's a good practice.

--
[ e d @ h a l l e y . c c ]

[reply]