Reply to thread

Message: [QUOTE="Art Sackett, post: 709297"] Keep in mind that you don't want to leave fatalsToBrowser in place once you fully deploy. There are two downsides: 1. The whole world can see your error messages, which might give hints about exploitable bugs. 2. It adds processing overhead to every invocation. Only use it while debugging/testing, then comment it out. If you want to avoid lots of bugs in the first place, always use the 'strict' pragma during development -- and again, comment it out when you release for deployment. [/QUOTE]