note 15093 deleted from pear.standards.comments by philip

There are many good debugging ideas here. All of them strike me as having their own use. It's worth pointing out that most of these debugging structures won't isolate a syntax problem that stops your script. Only comments work for that. Almost as good is the point that if you have several blocks of debugging code, you may wish to only show output from a few blocks at a time, so there is little gained in a "site wide" on/off switch. However, if your debugging a connection to a database, "site wide" could be useful on it's own, or in conjunction with commented debug code. This is because you know your code is good enough to run, even if it's the source of the problem due to SQL syntax or something like that. William of Scriptingbiz.com Man who run in front of car get tired. Man who run behind car get exhausted. Man who run beside car get along. P. S. If you leave your Fridge open to stay cool, you can probably use the back of the fridge for a bar-b-que. It's a great combination.