Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

Ok, I will do a workaround for my tests then. @Erich: you will have to do the same for the Jenkins slave if you want the test to complete without errors. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 04.02.2019 um 00:07 schrieb Rick McGuire : > > > > On Sun, Feb 3, 2019

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

On Sun, Feb 3, 2019 at 5:29 PM P.O. Jonsson wrote: > This is strange, a week ago all test passed on an ooRexx installation > installed to the standard place. I have cloned the installation setup for > the Jenkins slave for macOS and it should be the same there. > > Or did you add these test

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

This is strange, a week ago all test passed on an ooRexx installation installed to the standard place. I have cloned the installation setup for the Jenkins slave for macOS and it should be the same there. Or did you add these test about a week (or less) ago? I can see that the library

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

In that case, it will never work. The external libraries necessary to run those tests are NOT part of the installation process and never will be. Rick On Sun, Feb 3, 2019 at 12:04 PM P.O. Jonsson wrote: > I think the purpose of the test is to check the installation not the build > :-) > >

Re: [Oorexx-devel] Some questions on the test framework

Dear Erich, The problems with testing is the same also in revision 11711: [Framework exception] [20190203 22:23:06.321675] Type: Trap Severity: Fatal File: /Users/po/workspace/.../ooRexx/API/oo/FUNCTION.testGroup Line: 2130 Initial call of test container failed Condition: SYNTAX

Re: [Oorexx-devel] Some questions on the test framework

> Am 03.02.2019 um 19:44 schrieb Erich Steinböck : > > Hi P.O. > What is the purpose of the shell script setTestEnv.sh > It sets the environment for the tests to be able to find the framework and > its classes. > It is intended to run "sourced", with a leading dot, like this: . >

Re: [Oorexx-devel] Some questions on the test framework

Hi P.O. > What is the purpose of the shell script *setTestEnv.sh* > It sets the environment for the tests to be able to find the framework and its classes. It is intended to run "sourced", with a leading dot, like this: . ./setTestnv.sh (both leading dots are intended) setTestEnv also sets

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

I do not want to exclude the FUNCTION test group, that was not the issue. I think NOW is a good time to fix those small annoying things, including updating the readme for 5.0.0. Rather than work around the problems I would prefer to fix them once and for all. It is not THAT much missing so… PS

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

For a clean run of the installed use … rexx testOORexx.rex -s -X native_API -x FUNCTION.testGroup And do not bother about the setTestEnv.sh Also the instruction in the readme are just plain wrong They say to invoke it as a command … which implies that the changes to the environment are

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

Everything works if You run the tests from the Build directory rather than using the installed rexx Cheers E > On 3 Feb 2019, at 14:37, P.O. Jonsson wrote: > > Hi Erich, > > Before I could try ooRexx was already on r11710 and the problem persists. > Could it be that the changes in r11709

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

Dear Erich, For macOS (Darwin) it does not do its job at all, since the settings are not persistent. I am preparing another Email regarding this and other things related to the test framework, give me five minutes to finish it, ok? I need to understand this in detail when I do my test cases

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

OpenIndiana - r11710 [Framework exception] [20190203 08:58:33.780623]   Type: Trap Severity: Fatal   File: /export/home/agrellum/test/ooRexx/API/oo/FUNCTION.testGroup   Line: 2130   Initial call of test container failed   Condition: SYNTAX     Unable to load library "orxfunction"

Re: [Oorexx-devel] Ad ooRexx pipe-samples

He completely redid how those samples function and moved them well away from their original intent. I'm not really interested in incorporating those changes. Rick On Sun, Feb 3, 2019 at 7:36 AM Rony G. Flatscher wrote: > has another pipe-related >

[Oorexx-devel] Ad ooRexx pipe-samples

has another pipe-related patch by Matthé van der Lee from December 3rd 2018, which might have been overlooked. Just in case a reminder. Here is his statement: "For my own amusement, I have rewritten the pipe.rex sample, and included support for

[Oorexx-devel] Break up "rexxpg.pdf" into an "ooRexx Primer/Introduction" and a separate "C/C++ Programming Interfaces for ooRexx"?

For unknown reasons the "Programmer Guide" of ooRexx, "rexxpg.pdf", includes a primer for ooRexx and the documentation for savvy C/C++ programmers. If a newcomer is looking for an introduction into ooRexx it would be great if there was a specific pdf-book for it, like "ooRexx Primer -

Re: [Oorexx-devel] Variable Reference APIs

On Sun, Feb 3, 2019 at 5:52 AM Erich Steinböck wrote: > The API returns references to the object variable in the currently active >> object, which in this case is the tester object instance >> > Well, of course . .thanks > > I've got further questions: > oorexxapi.h has a #define

[Oorexx-devel] Ad Unix-based installations missing ooRexx samples and the ooRexx documentation ...

The Unix based installations do not come with the IMHO extremely import 1) ooRexx samples and 2) the ooRexx pdf documentation! Is there any convention to allow installing 1) and 2) with the base ooRexx installation? Or would there be a possibility to have an additional installation package that

Re: [Oorexx-devel] Variable Reference APIs

On Sun, Feb 3, 2019 at 7:07 AM Erich Steinböck wrote: > Trace shows the variable reference operator as "&" (as it was initially > proposed) > Should this now be changed to ">", resp. "<" ? > > Yes, missed that change when we finally resolved what character is used. > Do we really want to have

Re: [Oorexx-devel] Variable Reference APIs

Trace shows the variable reference operator as "&" (as it was initially proposed) Should this now be changed to ">", resp. "<" ? Do we really want to have both "<" and ">" as reference operators? I'd vote for reducing this back to only one. I like ">A" as "points-to A" ~~~ 1 *-* a = >b >O>

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

Hi P.O., revision [r11709] fixes the issue that ::requires can't find FUNCTIONPackage.cls On Sun, Feb 3, 2019 at 11:43 AM P.O. Jonsson wrote: > I did not receive any feedback on this question. Can someone please have a > look? I can not figure out what is wrong and it is NOT in my setup, the >

Re: [Oorexx-devel] r11708 - Could not find file "FUNCTIONPACKAGE.CLS"

revision [r11709] fixes the issue that ::requires can't find FUNCTIONPackage.cls ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Variable Reference APIs

> > The API returns references to the object variable in the currently active > object, which in this case is the tester object instance > Well, of course . .thanks I've got further questions: oorexxapi.h has a #define REXX_VALUE_RexxVariableReferenceObject, and NativeActivation seems to have

Re: [Oorexx-devel] Problems with testgroup FUNCTION.testGroup

I did not receive any feedback on this question. Can someone please have a look? I can not figure out what is wrong and it is NOT in my setup, the same error occurs on the Jenkins MAC slave currently, although it is reported as a „Success“, Here is the same output from the last Jenkins test

Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

Hi Michael, I didn't miss your reply, I just wouldn't know what could be wrong here. I recreated your setup as accurately as possible on my Ubuntu 16.04 VM and cmake runs successfully for me. ~~~ erichst@erich-vm:/$ md -p /kunden/homepages/35/d157794216/htdocs erichst@erich-vm:/$ cd