Re: debugging

On Wed, 2005-01-19 at 05:51, Marek Kilimajer wrote: > Justin French wrote: > > On 19/01/2005, at 5:36 PM, William Stokes wrote: > > > >> I would like to add some debugging/info code to my pages. In test > >> environment of course. Any ideas how to do this? I mean for example to > >> print > >> to a web page the line number when the script fails or something like > >> that. > >> It's a pain on the **s to hunt typo's by just reading the source over and > >> over again. > > > > > > William, > > > > I start by trying to programatically find out if I'm in a development or > > production environment and setting a constant DEV to true or false. For > > me, I development things on my desktop Mac, so the server and client are > > the same machine, and share the same IP address. So my check for DEV is > > if the client IP and server IP match. > > > > <? > > define('DEV',($_SERVER['REMOTE_ADDR']==$_SERVER['SERVER_ADDR'])); > > ?> > > Interesting. So I just need to use the same hosting server as you do and > your scripts will tell me interesting facts ;) > > I use simple define('DEBUG', true'); in the main config file where also > database login info is stored. > for complicated stuff I will usually place if $(DEBUG >N ){echo stuff} lines in the code so I can easily print interesting stuff in various parts of the script then if I hit a problem place a $DEBUG=1; or whatever level I want at the top of the script; This way I can turn it off and on without making code changes other than setting $DEBUG = 0; when moving to production. This causes some additional work in production but I suppose if I had that many ifs in there I could write a script to remove the $DEBUG { } blocks from the code during the move to production. Since we are on the topic, does anyone have such an animal? If I write one, would anyone be interested in it? Bret