It's created as a temporary file that is automatically removed.
But you just as well create any single-line nop file and use it to test
self~q is used to quote the file name if it should contain any space
Also you could test with standard OS command, like cat or echo
On Mon, Dec 10, 2018 at 8:26
r11588
say self~q(source~fullName)
/export/home/agrellum/oorexx-test/ooRexx/utilities/rexxc/test_rexxc.rex
I am not sure this file is being created for me.
Is it a in memory only thing?
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge
Will try writing some code but testgroup states OK.
agrellum@openindiana:~/oorexx-test$ ./testOORexx.rex -R
ooRexx/base/keyword -f address
Searching for test containers..
Executing automated test suite..
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRe
This looks very strange. From the trace I can see that
"rexxc
/export/home/agrellum/oorexx-test/ooRexx/utilities/rexxc/test_rexxc.rex"
does produce output when run as a normal no-WITH command, but not when run
with WITH OUTPUT STEM S.
I assume that ADDRESS.testGroup has passed all tests.
Can you
DUP and MINUS WITH;
New line to for NOP or ?
::resource "nop;empty 0" or ?
::resource "nop" ?
Searching for test containers..
Executing automated test suite 96 *-* source =
.TemporaryTestFile~new(self, self~testSource)
>E> .TEMPORARYTESTFILE => "The TEMPORARYTESTFILE class"
I can't see why no output lines would show up in stem s.
Can you try things like:
duplicating line 99 and removing the WITH .. part on the first of the two
lines so that we see the output from running the simpler instruction
address "" "rexxc" self~q(source~fullName)
The resource 'EMPTY 0' is speci
agrellum@openindiana:~$ rexxc qdate.rex legal.rexc
Open Object Rexx Version 5.0.0
Build date: Dec 7 2018
Addressing mode: 64
Copyright (c) 1995, 2004 IBM Corporation. All rights reserved.
Copyright (c) 2005-2018 Rexx Language Association. All rights reserved.
This program and the accompanying mat
Jason,
the test statistics repeat if there are any test failures. This works as
designed.
Re rexxc test failures:
Does rexxc print version/legal stuff if you run it against a Rexx program?
Can you "trace i" one of the failing methods?
On Fri, Dec 7, 2018 at 10:15 AM Jason Martin wrote:
> r1157
r11579
agrellum@openindiana:~/oorexx-test$ ./testOORexx.rex -X native_api
Searching for test containers
Executing automated test suite.../usr/bin/sh: line 1: zxyabc: not found
/usr/bin/sh: line 1: zxyabc: not found
...
.
