Hi there,
René V. Jansen has used the ooRexxUnit framework and
the oorexx unit tests on his port of 3.1.1 gamma to Mac
OSX and informed me of failures in the encode64 tests
(implemented in the test unit
"oorexxunit\ooRexx\base\class\ooRexx.Base.Class.String.testUnit")
and traps.
Therefore I used the latest CVS and built a Windows
version of the interpreter. Running the test units
causes a trap (with no further information and short of
a set up debugger/debugging environment, I only was
able to figure out the file containing the test which
causes the trap; it is the file
"ooRexx.Base.Class.String.testUnit").
I asked René to also file a bug, as he might be able to
supply more information.
In the meantime you could check out the ooRexxUnit
framework and the unit tests, e.g. (Please watch out
for line breaks):
cvs -z3
-d:ext:orexx@oorexx.cvs.sourceforge.net:/cvsroot/oorexx
co -P oorexxunit
cvs -z3
-d:ext:orexx@oorexx.cvs.sourceforge.net:/cvsroot/oorexx
co -P oorexxtest
[Just checked my latest changes of ooRexxUnit into CVS.]
You can run all testunits recursively, if you have your
path set to the
oorexxunit files "OOREXXUNIT.CLS" and "runAllTests.rex"
and execute the
following command from the root of "oorexxtest":
runAllTests.rex -r
This way you should be able to run the same set of
tests as René and I have been employing.
Regards,
---rony
Anonymous
Logged In: YES
user_id=1125291
The problem was caused by encoding characters greater than
0x7f, which got interpreted as a negative number that was
sign extended and used as an array index.