Re: How to best have statements execute only during dev/testing?

2006-01-10 Thread Ben Evans
On Tue, Jan 10, 2006 at 05:44:45PM +0100, Paul Johnson wrote: This isn't an answer to your question, but in general production is the environment in which your code will be exposed to the data and conditions which have had the least testing, and to which you will have the least access and

Re: How to best have statements execute only during dev/testing?

2006-01-10 Thread dakkar
Matisse Enzer wrote: The trick I want is that if my code is running in a production environment (perhaps determined at compile-time) then I want my Devel::Assert stuff to basically disappear. So the question is, what is the lowest-impact way to do that? This entry in BooK's use.perl journal

Re: How to best have statements execute only during dev/testing?

2006-01-10 Thread A. Pagaltzis
Hi Ben, * Ben Evans [EMAIL PROTECTED] [2006-01-10 18:20]: I'd make a slightly stronger statement than that: If you were congenitally insane, wilfully stupid or drunk, you could consider a source filter for this. Depends. Additive filters that the same code can run without are sane when used