RE: try catch issue

[Nate Nielsen]

“but we are dealing with a lot of pre-existing modules, so going back to each one is time consuming and not an option.”   This is the best option--  If you change the modules as you go, it wont be so bad.  If you think about it, the second time you use one module with the error catching in it, you will have saved yourself time from having to do your error checking again outside the module next time.   The term “module” would suggest you are re-using code – you’re defeating that purpose of course if you have to repetitively program your error control outside the module itself every time you want to call it.  –that option sounds more time consuming to me in the long run.   =)   Nate Nielsen [EMAIL PROTECTED]       From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schreck, Thomas (PPC) Sent: Friday, October 29, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: try catch issue   We arrange modules in a layout and programmatically generate the layout into a .cfm page.  We are using <cfimport> tag to call the modules instead of <cfmodule> because <cfmodule> is slow.  Anyways, the issue at hand is how to best manage when a module produces an error.  Ideally, we would like to have the module handle this itself, but we are dealing with a lot of pre-existing modules, so going back to each one is time consuming and not an option.   That said, what do you think about wrapping a <cftry>/<cfcatch> around each module call within the programmatically generated page?  How costly is <cftry>/<cfcatch> in terms of performance?   Thanks -   Tom Schreck 817-252-4900 [EMAIL PROTECTED]   I have not failed.  I've found 10,000 ways that won't work.   - Thomas Edison