On 3/28/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Keep taint mode on in dev, so you can identify your issues in
> development, then turn in off in prod.
Is that actually the generally recommended approach?
It's hard to know for sure that you've tried every code path in dev,
even if you do use coverage analysis.
I think the reality though is that hardly anyone uses taint mode.
It's a lot of work.
I know there are some people that argue that warnings should also be
turned off in prod
Those people are nuts. Warnings give very valuable feedback about
unforeseen errors in prod, and the only risk is a larger log file.
- Perrin
