After having gone through the code and running the RXTRC Java exit handler the traceObject works
there as well. Not sure why the objectname gets displayed in the testbinaries test case rather than
the makeString.
Anyway, will adjust the testcase accordingly as there seems to be no need to change anything in the
native code.
---rony
On 13.03.2024 19:21, Rony G. Flatscher wrote:
There are two trace related tests in the test suite failing (all other pass):
[failure] 20240313 18:16:37.500000
Test: TESTIOEXITTRACE
Class: RexxStart.testGroup
File: ...\oorexx\test\trunk\ooRexx\API\oo\ProcessRexxStart.testGroup
Line: 244
Failed: assertEquals
Expected: 47 *-* call trace OFF
Actual: a TraceObject
[failure] 20240313 18:16:41.827000
Test: TESTIOEXITTRACE
Class: RexxStart.testGroup
File: ...\oorexx\test\trunk\ooRexx\API\oo\RexxStart.testGroup
Line: 248
Failed: assertEquals
Expected: 47 *-* call trace OFF
Actual: a TraceObject
The tests use the classic Rexx exit interface and it seems that in these cases where now an
instance of TraceObject gets returned instead of a string, then the result of sending "objectname"
gets used ("a TraceObject"), instead the traceObject should get "request('String')" gets sent to
it which would return the string "47 *-* call trace OFF".
---
Where should the change made in this case, in the testcase (it can be adapted to collect the
generated trace object and then return its traceLine entry instead of the trace exits generated
string "a TraceObject") or in native code? If in native code, where exactly should the change be
applied?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
