On 20/11/2017 20:15, Bernd Eckenfels wrote:
:
One thing which might be a problem: when doPrivileged does no longer
execute the Code in a seperate stack this has implications to the
runtime. The stacks will get deeper (and might even overflow (more
often)). So maybe this „no seperate stack“ function should be opt-out
(if implemented).
Are you assuming that the execution of the privileged action is done on
a different thread stack? The effect of doPrivileged is to set the top
of the privileged stack on the current thread stack, it gets restored
when the action completes. So I think there isn't anything to be
concerned about here.
-Alan
