Hi Bert,
I'm going to try and answer a number of your questions here. If I miss
some then just re-ask them.
You can uniquely identify the version of ooRexx you are running by using:
rexx -v
C:\work.ooRexx>rexx -v
Open Object Rexx Version* 4.2.0*
Build date: *Jan 30 2014*
Addressing Mode: 64
Provided you stick to using the official versions, which are the versions
downloadable from SourceForge, the version number, build date, and to a
degree the addressing mode uniquely identify which version you are using.
If you are sophisticated enough to build your own interpreter, then we
figure you are sophisticated enough to keep track of what version you are
running.
For 4.2.0 we are in a beta phase and as we progressed through the phase,
the official builds have been placed in differently named directories on
SourceForge. When we placed a new version of the beta on SourceForge, we
removed the obsoleted one. In addition we posted an announcement each time
we did so.
You many want to subscribe to ooRexx Announcements at:
https://sourceforge.net/p/oorexx/mailman/?source=navbar
Although the announcements are always posted on this User list also.
We know you were not using release candidate 2, the latest, from an earlier
e-mail of yours:
Line from my run: Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04* 19 Jan*2014
As far as ooTest, which is my name for the test suite, goes, you can get a
print out by doing:
C:\work.ooRexx\wc\ooTest\4.x>testOORexx.rex -n
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 30 Jan 2014
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
Tests ran: 0
Assertions: 0
Failures: 0
Errors: 0
Skipped files: 0
Total time: 00:00:00.001000
So, I don't think there is any need to change anything there.
As far as your other suggestions relating to the test suite, options etc.,
they are appreciated.
But the fact of the matter is that only Rick and I really use the test
suite and its current state is sufficient for our use. If one of us sees a
need for something we add it.
When we first came up with the test suite we tried, hard, to get the
general ooRexx user to help with it by running it and more importantly by
contributing test cases. That effort was particularly useless waste of
time, in my view, and I no longer spend time on it.
However, the only reason there is a ooTest-4.2.0-snapshot06.zip today is
that 1 user showed interest in running the test suite last weekend, so I
produced a current snapshot.
If more users showed interest in using the test suite, the developers would
be more open to adding enhancements.
If course, all ooRexx users are encouraged to implement any enhancement
they would like and submit a patch for it. Or to request an enhancement at:
https://sourceforge.net/p/oorexx/feature-requests/
Some other miscellaneous answers. The fourth number in 4.2.0.9860 is the
svn revision number and can be somewhat misleading to people that do not
understand Subversion. In particular, a different svn number quite often
does not mean a difference in the code base used to build the software.
Adding it to the name, in my opinion, is likely to only cause more
confusion.
"I still would like to see the "-x" flag and a method to determine the
parameters for -X in the testing program."
The small -x is a valid suggestion. I believe the basic framework for it
already exists in the test suite, but the implementation is not finished.
Use help testTypes to get the parameters for -X:
C:\work.ooRexx\wc\ooTest\4.x>testOORexx.rex help testTypes
testOORexx version 1.1.0 ooTest Framework version 1.0.0_4.0.0
All test types:
Doc_example_noise Unit_long Framework_example Doc_example Unit Gui Ole
Sample Gui_sample Native_api Tcpip
Default test type set:
Doc_example Native_api Unit_long Sample Gui Gui_sample Ole Unit
Default exclued test type set:
Doc_example_noise Framework_example Tcpip
C:\work.ooRexx\wc\ooTest\4.x>
Use help topic to see what topics are available for extended help:
C:\work.ooRexx\wc\ooTest\4.x>testOORexx.rex help topic
testOORexx version 1.1.0 ooTest Framework version 1.0.0_4.0.0
Detailed help subjects (case insignificant) are:
testTypes
--
Mark Miesfeld
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
