> What does efficiency have to do with it?

You tell me:
" I can show you many ways to rewrite it and be more efficient without
using cfabort."

> You will not change my mind on the use of cfabort, pure and simple.

I'm not really interested in changing your mind. I am interested in
disagreeing with what I think are incorrect blanket statements like
"never use CFABORT".

> CFError was introduced to capture errors, and it does a good job of it too.

That's very true, but I'm not sure how it's especially relevant here.
If you simply want to abort processing, CFABORT is perfectly good for
this. If you want to show the user a bit of text before you abort
processing, CFABORT still is perfectly good for this.

> But my question is if you are not using onRequestEnd.cfm what does it matter 
> if you
> use cfabort or not? Personally I would tentd to not use it ...

Yes, fine. The key word there is "personally". But you seem to make
the jump from personal preference to defining that preference as a
best practice, and that's what I object to.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
GSA Schedule, and provides the highest caliber vendor-authorized
instruction at our training centers, online, or onsite.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345838
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to