Re: [Oorexx-devel] RFC: suggestion a solution for getting the caller stackframe of a spawning activity

2024-08-18 Thread Rony G. Flatscher
On 18.08.2024 15:18, Rony G. Flatscher wrote: On 18.08.2024 14:44, Rick McGuire wrote: One thing you've missed is that there are situations where there is no spawning activation. For example, from native code, I can attach a thread, create a message object and send it a START message. In that s

Re: [Oorexx-devel] RFC: suggestion a solution for getting the caller stackframe of a spawning activity

2024-08-18 Thread Rony G. Flatscher
On 18.08.2024 14:44, Rick McGuire wrote: One thing you've missed is that there are situations where there is no spawning activation. For example, from native code, I can attach a thread, create a message object and send it a START message. In that situation, there is no activation to create a st

Re: [Oorexx-devel] RFC: suggestion a solution for getting the caller stackframe of a spawning activity

2024-08-18 Thread Rick McGuire
One thing you've missed is that there are situations where there is no spawning activation. For example, from native code, I can attach a thread, create a message object and send it a START message. In that situation, there is no activation to create a stack frame from. Also, the stack frame in que

[Oorexx-devel] RFC: suggestion a solution for getting the caller stackframe of a spawning activity

2024-08-18 Thread Rony G. Flatscher
With the introduction of TraceObject it becomes possible to create and store trace logs for further analysis. In March, I started to create a little tracetool.rex/tracutil.cls to help the Rexx programmers analyze their code. Testing and analyzing what can be inferred, it turned out that in the c