Not saying it's a good thing, just laying out what it's accomplishing.
Seeing as Flash generates some pretty ugly looking runtime errors, I
usually like to display errors on my own terms, such as
catch (err:Error){
ErrorManager.showError("There was a problem communicating with the
server, please try again later");
}
On Tue, Mar 3, 2009 at 7:19 PM, Dave Watts <[email protected]> wrote:
>> Now considering there is no code in the 'catch' block,
>> there can be absolutely no benefit whatsoever to using
>> try-catch-finally in the above instance.
>
> Well, it'll swallow the exception; that might be considered by some to
> be a benefit, although it's bad form to handle exceptions that way.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
>
> Fig Leaf Software provides the highest caliber vendor-authorized
> instruction at our training centers in Washington DC, Atlanta,
> Chicago, Baltimore, Northern Virginia, or on-site at your location.
> Visit http://training.figleaf.com/ for more information!
> - Show quoted text -
> _______________________________________________
> Flashcoders mailing list
> [email protected]
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
