From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc3.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Debugging Questions References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3217142471287612@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Dec 2001 10:41:12 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1008153672 193.71.66.49 (Wed, 12 Dec 2001 11:41:12 MET) NNTP-Posting-Date: Wed, 12 Dec 2001 11:41:12 MET Xref: archiver1.google.com comp.lang.lisp:22269 * "Chris Perkins" | I'll probably solve this problem in the short term by littering my code | with pprint and format statements, but I really hate to do this. Have you considered using a macro around such debug output forms to control the "debugging level" at which they emit output and to turn it off entirely when you think you no longer need it, without removing the debugging forms from the code? My prediction is that you really want to keep those debugging forms in there when you deploy, because you may find another bug and the ability to dump loads of debugging information by tweaking a variable in a running image may be very valuable. /// -- The past is not more important than the future, despite what your culture has taught you. Your future observations, conclusions, and beliefs are more important to you than those in your past ever will be. The world is changing so fast the balance between the past and the future has shifted.