Re: Lua C++ exception catching too broad.

[Sam Roberts <sroberts@...>]

On Tue, Aug 01, 2006 at 12:51:48PM -0400, Joe Smith wrote:
> "Joe Smith" <unknown_kev_cat@hotmail.com> wrote in message 
> news:eagvcd$m9n$1@sea.gmane.org...
> >
> >"Mark Hamburg" <mhamburg@adobe.com> wrote in message 
> >news:C0F144E9.48687%mhamburg@adobe.com...
> >>If you do that, I think it will probably leave the Lua state messed up.
> >>
> >>Mark
> >
> >Concurred. However, that is for the end user to deal with. Enigma,
> >the project in which I noticed that catch statement has reasons to do
> >this, and in all such cases will discard the lua state, automatically
> >assuming it is corrupted beyond repair.

Is it possible to be corrupted badly enough that it can't be closed? And
aren't memory leaks also possible?

Just curious.

Sam