I'm going to send you a developer build that has our initial implementation of try/catch for CFSCRIPT, as well as code to help identify error lines more precisely within CFSCRIPT (this stuff didn't make it into BD 6.1, but will be in 6.2 and BD.NET). This should help.
I'll do this when I get in to the office tomorrow (Wed). Ping me if you haven't received something from me by noon (17:00 GMT). Vince > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Milligan > Sent: Tuesday, June 29, 2004 6:39 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > > Unfortunately the cfdebugger tag doesn't help very much > because a lot of the stuff that's causing problems was > written using cfscript. > > The last entry in the log file generated by the cfdebugger tag is: > > tag.start=CFSCRIPT; L/C=(290,4); > File=C:/BlueDragon_J2EE_61/FarCry/fourq/fourq.cfc > > I already knew that from the exception information that was > displayed in the web browser. > > 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 Stephen Milligan > >Sent: Tuesday, June 29, 2004 2:29 PM > >To: [EMAIL PROTECTED] > >Subject: RE: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > > > >I wasn't aware of that Vince, > > > >Thanks for the heads up. > > > >I'm just about to put it through it's paces, so I'll report > back on how > >well it handled the stream of cryptic error messages that I've been > >fighting. > > > >A step-wise debugger would be very welcome if there was a good > >interface for it ;) > > > >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 Vince Bonfanti > >>Sent: Tuesday, June 29, 2004 2:19 PM > >>To: [EMAIL PROTECTED] > >>Subject: RE: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > >> > >>I wasn't aware of this difference. Have you tried using the > CFDEBUGGER > >>tag to trace execution? Charlie describes it in one of his blog > >>entries: > >> > >> http://bluedragon.blog-city.com/read/188000.htm > >> > >>It's also listed in the BlueDragon CFML Compatibility Guide > under "New > >>Tags". > >> > >>I know use of CFABORT is common for debugging, but it seems > crude and > >>dangerous. What if I could offer you a step debugger instead > >that would > >>allow you to set breakpoints, examine variable scopes > anywhere in the > >>call stack, etc.? > >> > >>Vince > >> > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Milligan > >>> Sent: Tuesday, June 29, 2004 6: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 > >>> > >>> -------------------------------------------- > >>> 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 Vince Bonfanti > >>> >Sent: Tuesday, June 29, 2004 1:39 PM > >>> >To: [EMAIL PROTECTED] > >>> >Subject: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > >>> > > >>> >Can anyone think of any legitimate use of CFEXIT or > CFABORT with a > >>> >CFFUNCTION? I can't: if the functions finishes normally use > >>> CFRETURN, > >>> >if abnormally use CFTHROW. > >>> > > >>> >I can't find any docs that say use of CFEXIT or CFABORT is > >>> allowed or > >>> >disallowed within CFFUNCTION. I'd be in favor or saying they're > >>> >disallowed, and have the CFML server > >>(BlueDragon/ColdFusion) throw a > >>> >syntax error ("illegal tag nesting", or some such) if > >>> they're attempted > >>> >to be used this way. > >>> > > >>> >Any thoughts? Am I missing something? > >>> > > >>> >Vince Bonfanti > >>> >New Atlanta Communications, LLC > >>> >http://www.newatlanta.com > >>> > > >>> > ---------------------------------------------------------- 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]
