[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: "*toclose" vs. sandboxes / embedded environments
- From: "Soni \"They/Them\" L." <fakedme@...>
- Date: Mon, 17 Dec 2018 10:59:27 -0200
On 2018-12-17 10:44 a.m., Roberto Ierusalimschy wrote:
This seems to me to be a significant decrease in the environment's or
sandbox's ability to control what happens in error cases. In my own
project, I am not even sure I can handle this safely; if the environment
can't exert any control over this feature, it might be impossible for me
to support 5.4 at all, which would be a great shame.
Can you give a more concrete example of how that would be a problem?
Would it be better to keep the original error after running the closing
(We have no strong reasons to raise the last error instead of the first
one; this is just how "most" languages (at least Java :-) do.)
Some sandboxes use errors for dealing with special stuff.
Arguably, they should be using coroutines, which I assume would not