Re: Lua C++ exception catching too broad.

["Joe Smith" <unknown_kev_cat@...>]

"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.  Really the basic complaint is that a library 
> (even
> one such as lua) really should not be using catch(...) and in this case it
> is.
> It is a trivial one line patch.

No further comments?

Will this change actually be made?

It does not break anything, and does fix what could be considered a bug
in lua, so it seems like it should be able to make it into the next point 
release.