I would mostly agree with Sean's comments on this. There are very few times when I would actually feel the need to use a debugger, but given the fun and games I've had over the last few days trying to get FarCry running on BlueDragon I can honestly say it would have saved me many hours of work. I think that I can can debug CFML code about as well as anyone, but the stuff I was getting the last couple of days was, as a good friend of mine used to say, like swimming through setting concrete.
In those rare cases where you do need a debugger it can save the cost of the product license just solve a single problem. I've run into that one on several occasions when I was brought in to do some pre-release load testing on bigger projects. I would have thought it would make more economic sense to have the debugger as a separate product that you can purchase and use as required - something more like a load test tool, but it's not my decision to make. On a more selfish note, the sooner I have access to a debugger the better. Anything that allows me to better understand what my code is _really_ doing is going to help me develop better code in the long run. Spike -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield >Sent: Thursday, July 01, 2004 9:14 PM >To: [EMAIL PROTECTED] >Subject: Re: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > >On Wed, 30 Jun 2004 03:10:46 -0400, Roland Collins ><[EMAIL PROTECTED]> wrote: >> Upon further thought, I should qualify my previous statement >about not using >> debuggers. I _should_ have said that I have not used a >debugger to *step >> through* code in years. Of course I know how to use >debuggers and of course >> I take advantage of what ever exception analysis tools are >provided by a >> given debugger when one is available, but I do not use >debuggers as a tool >> for stepping through code line by line. I have met far too >many programmers >> who are far too reliant on debuggers and have no idea how to >utilize good >> old-fashioned, time-tested trouble-shooting techniques. > >I'm with Roland here. I gave up using debuggers many, many years ago >as just not being a tools I found particularly useful. I could pretty >much always debug code faster 'by hand' than most programmers could >with a debugger. Go figure. > >Do I think a debugger for CF would be well-received? Yes, a lot of >CFers seem to want this (and many seem to miss the semi-functional >debugger that was previously available pre-MX). Do I think that a >debugger for CF is a high priority? No, I think that there are many, >many more enhancements that are more important. Should New Atlanta >build a debugger for BlueDragon? Only they can say, based on the >feedback from their customers. >---------------------------------------------------------- >You are subscribed to cfcdev. To unsubscribe, send an email >to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' >in the message of the email. > >CFCDev is run by CFCZone (www.cfczone.org) and supported >by Mindtool, Corporation (www.mindtool.com). > >An archive of the CFCDev list is available at >www.mail-archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
