Eval with ScriptContext ignores settings

[everestbt]

As with issue #67, when a ScriptContext is used it will ignore the settings chosen.

This is exposed by a currently ignored test: testQuitWithScriptContext()

My only proposed solution at the moment is to disallow this method with an UnsupportedOperationException, this does create backwards compatibility issues but with the current implementation it is unclear that this will be the result.

[Dennyjomiller98]

Is this still an issue?

I'm wondering as when trying to create a new sandbox and disable all functions except allowPrintFunctions(true), the other allowExitFunctions(false) seem to be ignored, allowing quit(); to run on the script.
Edit: For clarification, this is when using sandbox.eval(script, context);, without setting custom bindings.
Edit2: inject() gets me where I want without the use of .eval(script, context).

[mxro]

Hey @Dennyjomiller98 thank you for your comment!

Yes this is still an issue!