I’m thinking it might make sense to move the lock number to the stack frame
too.
Rick
On Mon, Apr 8, 2024 at 7:06 AM Rony G. Flatscher
wrote:
> On 03.04.2024 09:26, Chip Davis wrote:
> > Seems more Rexx-ish, unless its specification might conflict with a
> future usage of the term in
> > that c
On 03.04.2024 09:26, Chip Davis wrote:
Seems more Rexx-ish, unless its specification might conflict with a future usage of the term in
that context.
-Chip-
On 4/2/2024 4:19 PM, Rony wrote:
Another question: offline I got the suggestion to change the NR entry in TraceObject to NUMBER.
What do y
Seems more Rexx-ish, unless its specification might conflict with a
future usage of the term in that context.
-Chip-
On 4/2/2024 4:19 PM, Rony wrote:
Another question: offline I got the suggestion to change the NR
entry in TraceObject to NUMBER. What do you think?
___
As already mentoned one can get at OBJECT and SCOPE via the STACKFRAME entry.
In the case that the TYPE is METHOD one can fetch OBJECT via the TARGET entry,
in the case of a method one can in addition get SCOPE by sending the scope
message to the method executable. Therefore the two current entr
After making sure that TEST.testgroup and TEST_TestObject.testgroup work, I committed 12814 (code)
and 12815 (doc) to see whether all tests keep on running on all platforms via Jenkins.
---rony
On 29.03.2024 15:43, Rony G. Flatscher wrote:
While experimenting with TraceObjects for anaylsis
While experimenting with TraceObjects for anaylsis it seems that the following
would be an improvement:
* replace the OBJECTID entry with an OBJECT entry, storing the receiver/self
object: if needing
the identity hash value (e.g. for externalization) one can send it the
identityHash messag
