Re: [Oorexx-devel] ooRexx auto-update

2018-12-09 Thread Adrian Baginski 
Well, I'm using Windows 10 and the OS isn't updating ooRexx at all.

Ki
nd regards
Adrian


From: Enrico Sorichetti via Oorexx-devel 
Sent: Sunday, December 9, 2018 7:35:42 PM
To: Open Object Rexx Developer Mailing List
Cc: Enrico Sorichetti
Subject: Re: [Oorexx-devel] ooRexx auto-update

What operating system, how is ooRexx installed

It is the responsibility  of  the operating system software manager to setup 
the infrastructure
To check at predefined intervals the remote software repositories for updates

Enrico


On 9 Dec 2018, at 19:28, Adrian Baginski 
mailto:abagin...@live.de>> wrote:

Hi guys,

I was just wondering, why is there no auto-update functionality for the ooRexx 
package, where the user gets a popup to update to a newer version when it is 
available? Currently, I have to remove the entire ooRexx package and install 
another version in order to „update“ it, which can quickly become fatigueing 
and encourages most users to not update at all.

Kind regards
Adrian

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx auto-update

2018-12-09 Thread Michael Lueck 

Rony wrote:

Hmm, how about ooRexx looking up Sourceforge or git or RexxLA once an hour, 
once a day, once a  to see whether a new release is available



If this method... we best accommodate a flag in the instance installation to disable 
"phone home" for places/uses such is impossible. Such as deployments in DMZ 
environments.

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx auto-update

2018-12-09 Thread Rony 
Hmm, how about ooRexx looking up Sourceforge or git or RexxLA once an hour, 
once a day, once a  to see whether a new release is avalable and then 
giving some hint such that the user can initiate the update (download and 
update)?

—-rony

Rony G. Flatscher (mobil/e)

> Am 09.12.2018 um 19:35 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> What operating system, how is ooRexx installed 
> 
> It is the responsibility  of  the operating system software manager to setup 
> the infrastructure
> To check at predefined intervals the remote software repositories for updates
> 
> Enrico
> 
> 
>> On 9 Dec 2018, at 19:28, Adrian Baginski  wrote:
>> 
>> Hi guys,
>>  
>> I was just wondering, why is there no auto-update functionality for the 
>> ooRexx package, where the user gets a popup to update to a newer version 
>> when it is available? Currently, I have to remove the entire ooRexx package 
>> and install another version in order to „update“ it, which can quickly 
>> become fatigueing and encourages most users to not update at all.
>>  
>> Kind regards
>> Adrian
>>  
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx auto-update

2018-12-09 Thread Enrico Sorichetti via Oorexx-devel 
What operating system, how is ooRexx installed 

It is the responsibility  of  the operating system software manager to setup 
the infrastructure
To check at predefined intervals the remote software repositories for updates

Enrico


> On 9 Dec 2018, at 19:28, Adrian Baginski  wrote:
> 
> Hi guys,
>  
> I was just wondering, why is there no auto-update functionality for the 
> ooRexx package, where the user gets a popup to update to a newer version when 
> it is available? Currently, I have to remove the entire ooRexx package and 
> install another version in order to „update“ it, which can quickly become 
> fatigueing and encourages most users to not update at all.
>  
> Kind regards
> Adrian
>  
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
> 
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] ooRexx auto-update

2018-12-09 Thread Adrian Baginski 
Hi guys,

I was just wondering, why is there no auto-update functionality for the ooRexx 
package, where the user gets a popup to update to a newer version when it is 
available? Currently, I have to remove the entire ooRexx package and install 
another version in order to „update“ it, which can quickly become fatigueing 
and encourages most users to not update at all.

Kind regards
Adrian

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Advice for ooRexx test suite: when subclassing ooTestCase and defining a proper constructor then do not forget ...

2018-12-09 Thread Rony G. Flatscher 
The ooRexx test framework allows one to create a test group with test cases by 
simply subclassing
the class ooTestCase.

If the subclass has a need for a constructor (defines the method 'INIT'), then 
it is mandatory to
invoke the constructor in its superclass otherwise a runtime error will occur.

E.g. defining a Rexx test group named "defaultMethods.testGroup" like this:

... cut ...
::class "testDefaultMethods" subclass ooTestCase public

::method init
  expose pkgName
  say self
... cut ...

will cause an error like:


F:\work\svn\bsf4oorexx\trunk\bsf4oorexx.dev\testUnits\bsf4rexx\java8\defaultMethods>rexx
 defaultMethods.testGroup
  1722 *-* return fName
  1733 *-* return "testCase:" pp(self~getName) "(a" || addN(className) 
className || "@" || -  self~definedInFile")"
68 *-* say self
   *-* Compiled method "NEW" with scope "Object".
  1808 *-*   self~addTest(testCaseClass~new(name))
   516 *-* forward class (super) continue
   *-* Compiled method "NEW" with scope "Object".
  1503 *-*   suite = .ooTestSuite~new(tClass)
54 *-* testResult = group~suite~execute~~print
Error 98 running F:\work\svn\oorexx\test\trunk\framework\OOREXXUNIT.CLS 
line 1722:  Execution error.
Error 98.986:  Reference to unassigned variable "FNAME".

Unfortunateyl, the error message does not really point to the cause, that the 
superclass' 'init'
method was not invoked.
[Ultimately this error goes back to the fact that the ooRexx test framework 
added the "::OPTIONS
NOVALUE ERROR" directive sometimes after this directive was introduced to 
ooRexx (which in principle
is good).]

So, to save you (potentially a *lot* of) time: whenever you have a need for a 
constructor (the
method named 'init') in your test group, the *first thing* you should do is 
invoke the superclass
constructor to avoid such runtime errors, e.g. like this:

... cut ...
::class "testDefaultMethods" subclass ooTestCase public

::method init
  expose pkgName

  *forward class (super) continue /* let the superclass first initialize 
everything it needs */*
  say "self:" self
... cut ...

which would output in this case:


F:\work\svn\bsf4oorexx\trunk\bsf4oorexx.dev\testUnits\bsf4rexx\java8\defaultMethods>rexx
 defaultMethods.testGroup
self: testCase: [TEST_01] (a 
testDefaultMethods@F:\work\svn\testUnits\bsf4rexx\java8\defaultMethods\defaultMethods.testGroup)

---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

2018-12-09 Thread Jason Martin 

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-ooRexx_5.0.0(MT)_64-bit 6.05 8 Dec 2018
OS Name:    SUNOS
SysVersion: SunOS illumos-863275a46b.5.11

Tests ran:  75
Assertions: 241
Failures:   0
Errors: 0

File search:    00:00:00.011534
Suite construction: 00:00:00.002149
Test execution: 00:00:00.845515
Total time: 00:00:01.513260




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

2018-12-09 Thread Erich Steinböck 
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 test various commands (e. g. "rexxc", "echo", with and without
args) with and without WITH OUTPUT STEM S. to find out when WITH OUTPUT
STEM S. doesn't receive output although it is there in the no-WITH case?

It seems that the rexxc test group works on all other tested OS's, so this
issue is a bit of a surprise
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] OpenIndiana r11581 testsuite broken

2018-12-09 Thread Erich Steinböck 
>
> ./testOORexx.rex -X native_api
> Segmentation Fault (core dumped)
>

In rare cases we unfortunately still see segfaults in the first phase of
testOORexx, before the first test has started running.
The faults cannot easily be reproduced and we have been unable to track
them down.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Proposal: How about moving the sources for the binaries to the main source tree.

2018-12-09 Thread Enrico Sorichetti via Oorexx-devel 
> Converting this to an out-of-source build might be tricky, 


I beg to disagree …

No more tricky than the same for somebody who wants to build a rexx external 
function

And would like to detect automatically the proper compiler and linker flags

for the unix like environments 

the thing is automated by using pkgconf/pkg-config ( present in all the linux 
installations )
And having ooRexx build the proper oorexx.pc 
As it would be a courtesy just build it straight away
… not difficult at all to do

Or … less elegant 
In the CMakeLists parse the output of the command “which rexx”
And if the oorexx installation respect the STANDARD unix structure (bin, 
include,lib)
It will be easy to determine the proper flags 

E 

Here is a sample snippet

set( _lc_all "$ENV{LC_ALL}" )
set( ENV{LC_ALL} "C" )
execute_process( COMMAND which rexx
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
RESULT_VARIABLE _res
ERROR_VARIABLE  _err
OUTPUT_VARIABLE OOREXXPATH
OUTPUT_STRIP_TRAILING_WHITESPACE )
set( ENV{LC_ALL} "${_lc_all}" )

message( "@@RESULT  '${_res}' " )   
message( "@@RESULT  '${_err}' ")
message( "@@RESULT  '${OOREXXPATH}' " ) 

if( NOT "${_res}" STREQUAL "0" )
message( FATAL_ERROR "
 Open Object Rexx is not installed" )
endif()

get_filename_component( OOREXXHOME "${OOREXXPATH}" REALPATH )

message( "@@Include flag'-I${OOREXXHOME}/include'" )
message( "@@Library flag'-I${OOREXXHOME}/lib'" )



Which when used in the CmakeLists gives ( when rexx is found )

@@  RESULT  '0' 
@@  RESULT  '' 
@@  RESULT  '/opt/ooRexx_Alt/bin/rexx' 
@@  Include flag'-I/opt/ooRexx_Alt/bin/rexx/include'
@@  Library flag'-I/opt/ooRexx_Alt/bin/rexx/lib'


And when not found …

@@  RESULT  '1' 
@@  RESULT  '' 
@@  RESULT  '' 
CMake Error at CMakeLists.txt.test:18 (message):
  

   Open Object Rexx is not installed
Call Stack (most recent call first):
  CMakeLists.txt:131 (include)


-- Configuring incomplete, errors occurre___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel