Re: [Oorexx-users] -l flag

[Mark M. <mie...@gm...>]

On Sun, Feb 16, 2014 at 2:17 PM, Bertram Moshier
<ber...@gm...>wrote:

>
> Again thank you for the -l flag. Unfortunately, either I'm not
> understanding it or found a bug.
>

You found a bug.  I've fixed it, but I'm not going to do a new snapshot.
 You can either live with it, knowing the log file will always be named
ooTest.log, or you could download the fixed file directly from the svn
repository.  Try this URL:

https://sourceforge.net/p/oorexx/code-0/HEAD/tree/test/branches/4.2.0/trunk/worker.rex

In the upperish-left there is a link to "download this file"  Replace the
worker.rex file in the snapshot with the new file from SourceForge.

>
> A couple of questions:
> (1)  Is the output suppose to appear on both the screen and in the log
> file?
>

Yes, I want the output to always be printed to the screen.  If you want,
you can use the -l option to also put it in a log file.


> (2)  Is the log file suppose to contain everything that would appear on
> the screen or just some of it?
>

No, only the results are put in the log file.



> I ask because I'm wondering:
>  (2A)  When using the "-s" option should all that output be in the log
> file.
>

No.  The output from the -s option is just chaff.  The -s option is only
useful in rare cases, and the only useful output from it is the last line
printed.


>  (2B)  When not using the "-s" option should the many "......." and other
> stuff also be in the log file.
>

No.  All that output is just junk, throw it away.  The "...." are just
printed to show that the test suite execution is not hung, really just that
the interpreter is not hung.  You can use one of the -U flags to suppress
the dots:

  -u  -DsuppressTestcaseTicks=bool  Do not show ticks during test execution
  -U  -DsuppressAllTicks=bool       Do not show any ticks


> (3) Would it be possible to have the output only go to the log file?
>

I'm not in favor of that.  If you want to do that, then just do it for
yourself:

C:\work.ooRexx\wc\ooTest\4.x>testOORexx.rex -X native_api > myPersonal.log
2>&1

will redirect all output into your personal log file, myPersonal.log.  Just
know up front that at least 4 test cases will fail, as of today.  Maybe
more in the future if test case are added that depend on having a console
to work with.

The design of the test suite is for the output to be brief and concise.
 I'm not interested in seeing all the chaff along with the results.  Except
in rare cases, like the crash you reported, all I want to see are the
results.  ;-)

--
Mark Miesfeld