Ah I think I misread the original post. I thought this was a general discussion on handling cfcs which for some reason or another contain an error. How I use custom I prefer exceptions to bubble up to the application.cfm where cferror can inform me of the error. What I wrongly thought the argument was a choice between having CFCs wrapped in a try catch block or having them return a structure indicating a fatal error has occurred.
Kola >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf Of Thomas Chiverton >> Sent: 16 July 2003 16:56 >> To: [EMAIL PROTECTED] >> Subject: Re: [CFCDev] Stand-Alone CFCs? >> >> On Wednesday 16 Jul 2003 16:26 pm, Kola Oyedeji wrote: >> > the overhead (albeit quite small) involved in wrapping code in a >> > try/catch block I would prefer to use the structure with error message >> > route. >> >> the cferror tag provides a top level exception catcher, that means you >> don't >> need to do this, except where you know the code may sometimes fail, and >> can >> either taking action to fix it, or wish to tell the user it failed. >> >> -- >> Thomas C >> Advanced ColdFusion Programmer >> >> HANDLE WITH EXTREME CARE: This Email Contains Minute Electrically Charged >> Particles Moving at Velocities in Excess of Five Hundred Million Miles >> Per >> Hour. >> PLEASE ALSO NOTE: I don't speak for the company that sent this. >> >> ---------------------------------------------------------- >> You are subscribed to cfcdev. To unsubscribe, send an email >> to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' >> in the message of the email. >> >> CFCDev is run by CFCZone (www.cfczone.org) and supported >> by Mindtool, Corporation (www.mindtool.com). ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
