personally, I try to avoid using error codes. We can be pretty
darn explicit when we throw our errors with the whole message thing
that I, personally, don't see the use of maintaining a list of codes.
I'm not saying codes are useless - it all depends on what you need to
do with the error that bubbles up from the throw - but I don't have
much use for them. Though, technically, I suppose you could say
my explicit string that defines the error and explains it is an error
code in it's own right.
For instance:
<cfthrow
type="AREA.MISSING" message="The requested area does not exist"
detail="areaID=#arguments.areaid#" />
Bill
--
[EMAIL PROTECTED]
http://blog.rawlinson.us
If you want Gmail - just ask.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
- Re: [CFCDev] Throwing Errors From CFCs Bill Rawlinson
- Re: [CFCDev] Throwing Errors From CFCs Sean Corfield
