that's incorrect, actually. it will catch them in the order
defined. so if there is an ALL first, there will never be
any other. basically, it starts at the first CATCH, compares
exception types. if it is a match, that handler occurs, if
not, it examines the next one in order, ad
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 1:20 PM
To: CF-Talk
Subject: RE: CFTRY / CFCATCH questions
that's incorrect, actually. it will catch them in the order
defined. so if there is an ALL first, there will never
I'd argue that you're best off putting TYPE=all last anyway,
though.
And on another note, if you use type=ANY instead of ALL, it
will work ;o) Sorry, I couldn't resist.
I love error handling in CF, especially in 4.5+, since it's very
advanced for a tag based language. One of the
There are no requirements on the order of cfcatch statements that I'm aware
of.
- Original Message -
From: Jeffry Houser [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, April 23, 2001 6:45 PM
Subject: CFTRY / CFCATCH questions
I know that at least one CFCATCH must be
Jeffry,
Your last statement prior to the closing try needs to be a catch. If you are
running multiple catches and you also want to catch all, the all statement
needs to come last.
- Chris
!---
Christopher Cortes |Coming
, until
the last catch (which should probably be an ALL JIC)
chris olive, cio
cresco technologies
[EMAIL PROTECTED]
http://www.crescotech.com
-Original Message-
From: Bryan LaPlante [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 23, 2001 9:00 PM
To: CF-Talk
Subject: Re: CFTRY / CFCATCH
6 matches
Mail list logo
