That was my experience as well. I have also found <Cfdump> to be a great tag for the purpose of debugging. I used to write lots of output code to figure out what's my variables contain - now it's a one step deal.
-----Original Message----- From: Neil Clark [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 7:23 AM To: CF-Talk Subject: RE: UltraDev Jeez! the debugger has never really worked to any sort of degree to make it useful (unline Director's real-time watcher/debugger which is a god send for debugging.) I personally tend to just use a well placed CFABORT when it all goes wrong to try and find a bug. If you know the code it generally is pretty easy to figure out where an error/bug crops up. N _________________________ _________________________ ____________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
