Thanks for bringing us back on track. The closure on this thread (since I started it), is that we decided to modify BlueDragon to mimic CFMX on this (so Adam, in spite of all our back-and-forth, you win). Even though I'm not sure CFEXIT within a CFC function makes sense, we decided to support it for a couple of reasons:
- CFEXIT within a CFFUNCTION-based UDF does make sense (as was made clear to me during this discussion), so it made our implementation easier to also support it within CFC functions. - It was easy to implement (it required changing one line of code). - The customer who originally reported the CFEXIT issue to us really, really wanted it to work that way (even though I'd didn't fully agree with his reasoning--but, he's paying the bills). The CFEXIT-within-CFFUNCTION changes will be in the first BlueDragon 6.1 hotfix (Spike, they're already in the private JARs I've sent you). We already support CFABORT the way CFMX does, so my bad for including that in the discussion. Thanks, Vince > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Barry L Beattie > Sent: Saturday, July 03, 2004 5:33 AM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] CFEXIT or CFABORT within CFFUNCTION > > > ('s funny, this thread has drifted twice now - debuggers, BD > v CFMX... so to bring it back) > > 1) NO to removing the functionality of CFEXIT/CFABORT. they > can come in handy just when you need them (no syntax errors, > no warnings, etc) > > 2) I'd leave it up to the programmer. For years I've lived > with the mantra of not having multiple exit points (I adheir > as best as the situation allows). it's as bad as Basic (& > VB)'s "GO TO" statements). > > but to change functionality on a whim / theoritical point of > view? no, definately not. > > my 2c > cheers > barry.b > -- ---------------------------------------------------------- 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]
