specifically. If it works well enough for you, that's all that matters.
However, there are some specific items that people may want to avoid
generally.
> I am not writing anything to the page, the output tag is
> there just to run another function. You can see it from
> function heading that the output is set to false.
In that case, why use CFOUTPUT at all? Why not just run the function?
<cfset my_function()>
> As for the use of cfcatch, maybe this was not a good example,
> but I want to give more detailed error messages and/or
> perform recover operation on error.
In your example, though, you're not returning an error at all - just a
string, which the calling program will have to interpret as an error. In
general, it's considered good to return errors from objects when those
objects fail. Those errors can be caught by the callers of the objects.
> A general cferror page would be just too general for what I
> need. I guess it all comes down to what one needs the code to
> do in a given situation.
This is true enough.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
