When I'm debugging, but don't want to abort midstream, I usually do a global search and replace swapping 'output="false"' to 'output="true" realoutput="false"', and then undo it when I'm done. Not real clean, and a bit of a pain when you've got a lot of CFCs (that all have to be recompiled and recached), but it does work.
Personally, I think CF's method makes more sense, though it's probably slightly slower. Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Milligan > Sent: Tuesday, June 29, 2004 3:05 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > > I use cfabort all the time when debugging apps. > > I've found it an absolute pain in the ass that BlueDragon behaves > differently to CFMX in this regard. > > In CFMX any time you have a cfabort inside a function, you > can use cfoutput > or cfdump before it in the same function call to show the > value of variables > at that point. In BlueDragon it respects the output attribute of the > function. > > If you're not inside a nested function call hierarchy you can > set the output > attribute of the function to true temporarily to get around > this, but if you > are inside a hierarchy you're in for debug hell. > > I've just about given up on trying to debug Farcry on > BlueDragon for this > very reason. > > Of course, if BlueDragon supported the cftrace tag that might offer a > possible solution to the output problem. > > Spike ---------------------------------------------------------- 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]
