Re: [Oorexx-devel] (Conceptual?) Bug introduced into ooRexx that hinders intercepting "::requires" with security manager ?

2017-01-09 Thread René Jansen
I have several thoughts on this: 1) we cannot just drop support for something that has been in there for such a long time 2) if we open this up, I really want to include the change for non-admin operation of rxapi in the 5.00 release So my vote is to have a good look at this, and not to decide

Re: [Oorexx-devel] (Conceptual?) Bug introduced into ooRexx that hinders intercepting "::requires" with security manager ?

2017-01-09 Thread Moritz Hoffmann
On Mon, Jan 9, 2017 at 4:34 PM, Rony G. Flatscher wrote: > Should I file a bug for this, such that this can be resolved for ooRexx > 5.0beta? Hi Roni, thanks for looking into this. I think the real question to ask is whether we still support the security manager or not. Changes related to the p

[Oorexx-devel] (Conceptual?) Bug introduced into ooRexx that hinders intercepting "::requires" with security manager ?

2017-01-09 Thread Rony G. Flatscher
The security manager's example in chapter 13 used to work on the "::requires" statement as well, sometimes in the past, if my memory serves me right. Analyzing what happens it becomes clear that .method~new, .method~newfile, .routine~new and .routine~newfile will initialize the supplied code (re