Yeah, same sort of idea; do an "as you go" capture of variables & stuff. I
think this is more of a good development practice, and that each person
might find their own specific way of implementing it. I'm not suggesting we
create another , hah, standard here; but it has helped me when I've had
'mystery' code that refuses to do what I want...
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Hal Helms [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, October 10, 2000 10:17 AM
> To: Fusebox
> Subject: RE: Do you use the debugger?
>
> Alan, I use something similar that logs to a text file (so I can quickly
> look at it). I first create a unique "requestID" so that I can identify
> various line items as belonging to the same http request, then I add the
> fuseaction, datetime, and there's a message field that's optional.
>
> On all my fuses, I use this:
> <cfif request.testing>
> <cf_LogTest message="#GetCurrentTemplatePath()# called.">
> </cfif>
>
> Having something that you can look at is way better than just trying to
> figure out what might be wrong.
>
> {redacted for brevity}
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
