That's an excellent point, but it doesn't necessarily apply when CFSETTING EnableSillinessOnly is true.
----- Original Message ----- From: "Dave Watts" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 2:25 PM Subject: RE: Confessions of a sloppy non-CFLOCKer > > <cfcatch type="Lock"> > > You all *are* enclosing your CFLOCKs in CFTRY/CATCH, aren't you? > > </cfcatch> > > Not unless there's something specific about that individual block of code, > that's different from other locks in general. That's what CFERROR > TYPE="EXCEPTION" is for! > > I'm sorry - I couldn't resist. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
