Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Dear all,

I will create a new thread for this discussion, ok?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 16.09.2018 um 18:37 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> Hello Rony, P.O
> 
> Why not consider Apple OS as a member of the *ix/*BSD family
> and install as it was done once into /opt/oorexx ?
> after all even SUSE - IIRC - suggest to install USER things in /opt
> 
> I am against installing into /usr/local , 
> too many are using homebrew and You all know how it clobbers the usr/local 
> directory
> 
> furthermore  ( I do not know about the BSF… thing ) oorexx is NOT an 
> application/framework  bundle
> so installing into the Application/frameworks  folders is just plain 
> illogic/inconsiderate
> 
> cheers 
> enrico
> 
> PS.
> my mention of the rexxcps  pseudo performance results
> was just to compare the consequence of building oorexx 
> without specifying the CMAKE_BUILD_TYPE
> ( the relevant cmake variables are empty - which implies NO optimization )
> and using CMAKE_BUILD_TYPE Release/RelWithDebInfo with the proper flags 
> about 2millions cps vs around 11millions cps
> 
> thats a common error when using cmake ( forgetting the CMAKE_BUILD_TYPE)
> the CMakeLists should fill the unsuffixed optimization flags with reasonable 
> defaults 
> ( I use the same values used for the RelWithDebInfo flags )
> 
> 
> 
>> On 16 Sep 2018, at 18:11, Rony G. Flatscher  wrote:
>> 
>> Dear P.O.:
>> 
>> On 16.09.2018 18:01, P.O. Jonsson wrote:
>> hmm, I would not install the entire ooRexx package into its own directory 
>> "ooRexx5.0.0" underneath
>> "/usr/local" (otherwise the "/usr/local" directory gets "cluttered" by third 
>> party installed
>> software). Rather I would install it to "/opt" and only link those ooRexx 
>> binaries constituting the
>> ooRexx interpreter from there to "/usr/local/bin" and "/usr/local/lib".
>> 
>> This is because "/usr/local" seems to not be meant for installing "third 
>> party packages", rather
>> "/opt" is meant for that. [Under MacOSX in addition the Apple advised 
>> location for installing
>> applications and frameworks would be a possible choice from which then links 
>> occur to
>> "/usr/local/bin" and "/usr/local/lib". The BSF4ooRexx MacOSX packager does 
>> that and honors the Apple
>> "Framework" and "Application" installation structure and links from those 
>> locations to
>> "/usr/local/bin" and "/usr/local/lib".]
>> 
>> Best regards
>> 
>> ---rony
>> 
>> 
>> 
>> ___
>> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Enrico Sorichetti via Oorexx-devel]

Hello Rony, P.O

Why not consider Apple OS as a member of the *ix/*BSD family
and install as it was done once into /opt/oorexx ?
after all even SUSE - IIRC - suggest to install USER things in /opt

I am against installing into /usr/local , 
too many are using homebrew and You all know how it clobbers the usr/local 
directory

furthermore  ( I do not know about the BSF… thing ) oorexx is NOT an 
application/framework  bundle
so installing into the Application/frameworks  folders is just plain 
illogic/inconsiderate

cheers 
enrico

PS.
my mention of the rexxcps  pseudo performance results
was just to compare the consequence of building oorexx 
without specifying the CMAKE_BUILD_TYPE
( the relevant cmake variables are empty - which implies NO optimization )
and using CMAKE_BUILD_TYPE Release/RelWithDebInfo with the proper flags 
about 2millions cps vs around 11millions cps

thats a common error when using cmake ( forgetting the CMAKE_BUILD_TYPE)
the CMakeLists should fill the unsuffixed optimization flags with reasonable 
defaults 
( I use the same values used for the RelWithDebInfo flags )



> On 16 Sep 2018, at 18:11, Rony G. Flatscher  wrote:
> 
> Dear P.O.:
> 
> On 16.09.2018 18:01, P.O. Jonsson wrote:
> hmm, I would not install the entire ooRexx package into its own directory 
> "ooRexx5.0.0" underneath
> "/usr/local" (otherwise the "/usr/local" directory gets "cluttered" by third 
> party installed
> software). Rather I would install it to "/opt" and only link those ooRexx 
> binaries constituting the
> ooRexx interpreter from there to "/usr/local/bin" and "/usr/local/lib".
> 
> This is because "/usr/local" seems to not be meant for installing "third 
> party packages", rather
> "/opt" is meant for that. [Under MacOSX in addition the Apple advised 
> location for installing
> applications and frameworks would be a possible choice from which then links 
> occur to
> "/usr/local/bin" and "/usr/local/lib". The BSF4ooRexx MacOSX packager does 
> that and honors the Apple
> "Framework" and "Application" installation structure and links from those 
> locations to
> "/usr/local/bin" and "/usr/local/lib".]
> 
> Best regards
> 
> ---rony
> 
> 
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rony G. Flatscher]

Dear P.O.:

On 16.09.2018 18:01, P.O. Jonsson wrote:
> This may be the explanation. Indeed „my“ installation now goes into 
> /usr/local/
>
> With the information from Enrico, I have also managed to create a pkg 
> installer using pkgbuild
> that can install to /usr/local so in principle this step could be added to 
> the build process.
>
> There are a number of differences to „my build“
>
> Pkgbuild does not generate the welcome screen, the license info etc whereas 
> my build have all that
> used to be also in the 4.1.2 installer
>
> Pkgbuild modifies the path to add
> /usr/local/oorexx5.0.0/bin:
> /usr/local/oorexx5.0.0/lib:
> /usr/local/oorexx5.0.0/share:
> /usr/local/oorexx5.0.0/include:
>
> Whereas  my build (the postinstall script) create symbolic links to those 
> places.
>
> My build have a preinstall script that removes an earlier installation in the 
> same place, the
> pkgbuild does not provide that (yet)
>
> @ Eric: Should I try to amend the build process on the Mac mini to include 
> this last step? That
> would provide an installer also if it is not perfect.
hmm, I would not install the entire ooRexx package into its own directory 
"ooRexx5.0.0" underneath
"/usr/local" (otherwise the "/usr/local" directory gets "cluttered" by third 
party installed
software). Rather I would install it to "/opt" and only link those ooRexx 
binaries constituting the
ooRexx interpreter from there to "/usr/local/bin" and "/usr/local/lib".

This is because "/usr/local" seems to not be meant for installing "third party 
packages", rather
"/opt" is meant for that. [Under MacOSX in addition the Apple advised location 
for installing
applications and frameworks would be a possible choice from which then links 
occur to
"/usr/local/bin" and "/usr/local/lib". The BSF4ooRexx MacOSX packager does that 
and honors the Apple
"Framework" and "Application" installation structure and links from those 
locations to
"/usr/local/bin" and "/usr/local/lib".]

Best regards

---rony



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

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Dear Rony,

This may be the explanation. Indeed „my“ installation now goes into /usr/local/

With the information from Enrico, I have also managed to create a pkg installer 
using pkgbuild that can install to /usr/local so in principle this step could 
be added to the build process.

There are a number of differences to „my build“

Pkgbuild does not generate the welcome screen, the license info etc whereas my 
build have all that used to be also in the 4.1.2 installer

Pkgbuild modifies the path to add
/usr/local/oorexx5.0.0/bin:
/usr/local/oorexx5.0.0/lib:
/usr/local/oorexx5.0.0/share:
/usr/local/oorexx5.0.0/include:

Whereas  my build (the postinstall script) create symbolic links to those 
places.

My build have a preinstall script that removes an earlier installation in the 
same place, the pkgbuild does not provide that (yet)

@ Eric: Should I try to amend the build process on the Mac mini to include this 
last step? That would provide an installer also if it is not perfect.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 16.09.2018 um 17:24 schrieb Rony G. Flatscher :
> 
> 
> On 16.09.2018 11:30, P.O. Jonsson wrote:
> ... cut ...
>> Regarding the performance I think that would need to be treated in another 
>> thread. I have created
>> a LOT of various builds, also comparing with builds from bsf4ooRexx. I have 
>> had different builds
>> from the same build date testeds where one build reports a tenfold speed 
>> over the other when you
>> run rexxcps.rex. However, using both builds to run real programs (rather 
>> complex and running for a
>> longer time) the „slower“ build performs 20-30% BETTER than the „faster“ 
>> one, so on MAC
>> rexxcps.rex is not conclusive. I suggest to open up a new thread for that 
>> discussion later, I have
>> observed is so many times and on at least 3 different machines that it can 
>> not be just me messing
>> it up. I guess one needs to compare library versions and compiler options 
>> but later, ok? Getting
>> an installer is more important.
> ... cut ...
> 
> This may have to do with rxapi on MacOSX to have to be started over and over 
> again.
> 
> In the past years problems with the rxapi plist file on MacOSX have been 
> pointed out repeatedly e.g.
> cf. the mailing threads with CVBruce's posting on 2010-12-24 who also later 
> pointed at the core
> problem on MacOSX cf. CVBruce's posting on 2011-02-20. In this posting (seven 
> years ago by now)
> Bruce reported at having written a work-around for that problem for rxapi on 
> MacOSX modelled after
> the work around put in place for AIX, but was told that someone would rewrite 
> it later.
> 
> If I am not mistaken, the ooRexx CMake file causes an 
> "org.rexxla.oorexx.rxapid.plist" to be used
> that points to "/usr/bin/rxapi" whereas the official location (after Apple 
> banned any non-system and
> non-Apple software to be installed into "/usr/bin") should be probably 
> "/usr/local/bin/rxapi" instead.
> 
> ---
> 
> In any case this MacOSX rxapi problem should be addressed once ooRexx 5.0 
> went GA.
> 
> HTH,
> 
> ---rony
> 
> 
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rick McGuire]

On Sun, Sep 16, 2018 at 11:33 AM Rony G. Flatscher 
wrote:

>
> On 15.09.2018 15:14, Rick McGuire wrote:
>
> On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher 
> wrote:
>
>> Two quick questions:
>>
>>- what is the current state of the ooRexx interpreter in the trunk:
>>does it have all the garbage collection enhancements applied already?
>>
>> This has already be integrated.
>
> Great, so I will turn to this version and try my (memory consuming) test
> units for BSF4ooRexx with it, as it may be the case that the large memory
> optimization may allow them to run faster.
>
>
>>- what is the state of ooRexx 5.0 beta: when will it be released
>>(companies and organisations won't usually install software dubbed/in the
>>state of "beta")?
>>
>> There are still a couple of features that need docs and tests written,
> plus we still don't have a Mac installer.  It will be released when it is
> released. The same answer you get every time you ask this question. If you
> wish it to be done faster, then pitch in with completing the remaining work.
>
> If there was something that I could really do, then please let me know.
>
> However, being on a few other opensource projects (the main one being
> BSF4ooRexx allowing ooRexx to use Java as if it was ooRexx and employing
> ooRexx as a scripting language) time resources are extremely scarce. [Also,
> for months I have been meaning to become active in the OpenJDK JavaFX
> project to improve the support for Java scripting languages, motivated by
> BSF4ooRexx. Due to an extremely steep learning curve - I would have to
> become able to learn the details of quite some powerful Java class sources
> and then to create the JavaFX modules after changing source code there - I
> have not been able to even start on that endeavor.]
>
> Having said that, if there are e.g. test units that should/need to be
> created then I would try to help out in that corner. If so, please advise.
>

bugs and enhancements still needing work are all on Sourceforge. If you
click in the 5.0.0 link in the sidebar on the left, you'll see all of the
items targetted for 5.0.0. The Pending Work Items column will indicate what
work still needs to be done. Incomplete items are the ones what don't have
"none" in that column.

Rick

>
> ---rony
>
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rony G. Flatscher]

On 15.09.2018 15:14, Rick McGuire wrote:
> On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher  > wrote:
>
> Two quick questions:
>
>   * what is the current state of the ooRexx interpreter in the trunk: 
> does it have all the
> garbage collection enhancements applied already?
>
> This has already be integrated. 
Great, so I will turn to this version and try my (memory consuming) test units 
for BSF4ooRexx with
it, as it may be the case that the large memory optimization may allow them to 
run faster.

>   * what is the state of ooRexx 5.0 beta: when will it be released 
> (companies and
> organisations won't usually install software dubbed/in the state of 
> "beta")?
>
> There are still a couple of features that need docs and tests written, plus 
> we still don't have a
> Mac installer.  It will be released when it is released. The same answer you 
> get every time you
> ask this question. If you wish it to be done faster, then pitch in with 
> completing the remaining work.
If there was something that I could really do, then please let me know.

However, being on a few other opensource projects (the main one being 
BSF4ooRexx allowing ooRexx to
use Java as if it was ooRexx and employing ooRexx as a scripting language) time 
resources are
extremely scarce. [Also, for months I have been meaning to become active in the 
OpenJDK JavaFX
project to improve the support for Java scripting languages, motivated by 
BSF4ooRexx. Due to an
extremely steep learning curve - I would have to become able to learn the 
details of quite some
powerful Java class sources and then to create the JavaFX modules after 
changing source code there -
I have not been able to even start on that endeavor.]

Having said that, if there are e.g. test units that should/need to be created 
then I would try to
help out in that corner. If so, please advise.

---rony

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

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rony G. Flatscher]

On 16.09.2018 11:30, P.O. Jonsson wrote:
... cut ...
> Regarding the performance I think that would need to be treated in another 
> thread. I have created
> a LOT of various builds, also comparing with builds from bsf4ooRexx. I have 
> had different builds
> from the same build date testeds where one build reports a tenfold speed over 
> the other when you
> run rexxcps.rex. However, using both builds to run real programs (rather 
> complex and running for a
> longer time) the „slower“ build performs 20-30% BETTER than the „faster“ one, 
> so on MAC
> rexxcps.rex is not conclusive. I suggest to open up a new thread for that 
> discussion later, I have
> observed is so many times and on at least 3 different machines that it can 
> not be just me messing
> it up. I guess one needs to compare library versions and compiler options but 
> later, ok? Getting
> an installer is more important.
... cut ...

This may have to do with rxapi on MacOSX to have to be started over and over 
again.

In the past years problems with the rxapi plist file on MacOSX have been 
pointed out repeatedly e.g.
cf. the mailing threads with CVBruce's posting on 2010-12-24 who also later 
pointed at the core
problem on MacOSX cf. CVBruce's posting on 2011-02-20. In this posting (seven 
years ago by now)
Bruce reported at having written a work-around for that problem for rxapi on 
MacOSX modelled after
the work around put in place for AIX, but was told that someone would rewrite 
it later.

If I am not mistaken, the ooRexx CMake file causes an 
"org.rexxla.oorexx.rxapid.plist" to be used
that points to "/usr/bin/rxapi" whereas the official location (after Apple 
banned any non-system and
non-Apple software to be installed into "/usr/bin") should be probably 
"/usr/local/bin/rxapi" instead.

---

In any case this MacOSX rxapi problem should be addressed once ooRexx 5.0 went 
GA.

HTH,

---rony



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

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Hello again Enrico,

I also use a tweaked CMakelists.txt but there are no fundamental differences. I 
have always assumed that I needed to control the pkg build from CMake, I 
understood pkgbuild to need files created by CMake. Now when I have read your 
mail there seems indeed to be a way forward. THANKS.

There is a number of warnings for deprecated stuff during the build on MAC , I 
guess it makes sense to try to go after those now?

Regarding the performance I think that would need to be treated in another 
thread. I have created a LOT of various builds, also comparing with builds from 
bsf4ooRexx. I have had different builds from the same build date testeds where 
one build reports a tenfold speed over the other when you run rexxcps.rex. 
However, using both builds to run real programs (rather complex and running for 
a longer time) the „slower“ build performs 20-30% BETTER than the „faster“ one, 
so on MAC rexxcps.rex is not conclusive. I suggest to open up a new thread for 
that discussion later, I have observed is so many times and on at least 3 
different machines that it can not be just me messing it up. I guess one needs 
to compare library versions and compiler options but later, ok? Getting an 
installer is more important.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 16.09.2018 um 11:12 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> Hello P.O
> 
> I am using a slightly modified CMakeLists 
> find attached the diffs 
> 
> 
> the command line used is 
> ( naturally after having created the build directory at the same level of 
> oorexx.alt )
> 
> cmake ../oorexx.alt -DCMAKE_INSTALL_PREFIX=/opt/oorexx 
> -DCMAKE_BUILD_TYPE=Release
> 
> but I am considering to build using
> cmake ../oorexx.alt -DCMAKE_INSTALL_PREFIX=/opt/oorexx 
> -DCMAKE_BUILD_TYPE=RelwithDebInfo
> 
> for unknown reasons sometimes the O3 optimization flag thrashes things
> and looking at various documents there is not too much difference between -O2 
> and -O3
> the -g flag is not that much intrusive and gives some debugging hints
> 
> after that the usual make && make install
> ( it would be nice to implement the ctest part of cmake, to provide some 
> basic tests )
> 
> the quirk is that the pkgbuild must be run pointing to the installed dir
> ( IIRC xCode builds a phony install into /tmp )
> 
> find attached also the plist built by   pkgbuild
> 
> cheers
> enrico
> 
> P.S.
> the BUILD TYPE is very important, without it the rexx performance sucks :-)
> 
> rexxcps.rex gives ( -DCMAKE_BUILD_TYPE=RelwithDebInfo )
> Performance: 11038575 REXX clauses per second ( TOP )
> and is normally higher than 1050
> 
> 
> 
>  
> 
> 
>> On 16 Sep 2018, at 10:29, P.O. Jonsson > > wrote:
>> 
>> Dear Enrico, can you please share with me your CMake command line? It would 
>> help me a lot. I use your CMakeLists.txt so I should be able to reproduce 
>> what you did.
>> 
>> Von meinen Macbook gesendet
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Enrico Sorichetti via Oorexx-devel]

Hello P.OI am using a slightly modified CMakeLists find attached the diffs the command line used is ( naturally after having created the build directory at the same level of oorexx.alt )cmake ../oorexx.alt -DCMAKE_INSTALL_PREFIX=/opt/oorexx -DCMAKE_BUILD_TYPE=Releasebut I am considering to build usingcmake ../oorexx.alt -DCMAKE_INSTALL_PREFIX=/opt/oorexx -DCMAKE_BUILD_TYPE=RelwithDebInfofor unknown reasons sometimes the O3 optimization flag thrashes thingsand looking at various documents there is not too much difference between -O2 and -O3the -g flag is not that much intrusive and gives some debugging hintsafter that the usual make && make install( it would be nice to implement the ctest part of cmake, to provide some basic tests )the quirk is that the pkgbuild must be run pointing to the installed dir( IIRC xCode builds a phony install into /tmp )find attached also the plist built by   pkgbuildcheersenricoP.S.the BUILD TYPE is very important, without it the rexx performance sucks :-)rexxcps.rex gives ( -DCMAKE_BUILD_TYPE=RelwithDebInfo )Performance: 11038575 REXX clauses per second ( TOP )and is normally higher than 1050

oorexx_svn.2.oorexx_alt.diff
Description: Binary data
 

com.oorexx.pkg.plist
Description: Binary data
On 16 Sep 2018, at 10:29, P.O. Jonsson  wrote:Dear Enrico, can you please share with me your CMake command line? It would help me a lot. I use your CMakeLists.txt so I should be able to reproduce what you did.
Von meinen Macbook gesendetHälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se

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

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Dear Enrico, can you please share with me your CMake command line? It would 
help me a lot. I use your CMakeLists.txt so I should be able to reproduce what 
you did.

Von meinen Macbook gesendet

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 15.09.2018 um 23:28 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> 
> 
>> On 15 Sep 2018, at 22:35, P.O. Jonsson > > wrote:
>> 
>> I fear that will be very difficult,
> 
> 
> difficult but not really impossible
> 
> I just run a quick and dirty test for my rexx  installed in /opt/oorexx
> 
> pkgbuild --identifier com.oorexx.pkg --install-location /opt/mytests --root 
> /opt/oorexx  oorexx.pkg
> 
> after that 
> 
> open oorexx.pkg 
> 
> the usual apple dialog appeared
> 
> and the installation proceeded
> 
> into /opt/mytests
> 
> a few things to investigate
> 
> but the approach looks workable
> 
> cheers
> enrico
> 
> 
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Enrico Sorichetti via Oorexx-devel]

> On 15 Sep 2018, at 22:35, P.O. Jonsson  wrote:
> 
> I fear that will be very difficult,


difficult but not really impossible

I just run a quick and dirty test for my rexx  installed in /opt/oorexx

pkgbuild --identifier com.oorexx.pkg --install-location /opt/mytests --root 
/opt/oorexx  oorexx.pkg

after that 

open oorexx.pkg 

the usual apple dialog appeared

and the installation proceeded

into /opt/mytests

a few things to investigate

but the approach looks workable

cheers
enrico



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

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Dear Rick,

I fear that will be very difficult, Apple have removed the possibility to 
generate such installers so using Cmake I do not think that can ever work. I 
have tried for a long time and to my knowledge that is not doable. I hope 
someone with more knowledge on Cmake can prove me wrong.

Personally I do not think the feature of having a pkg installer created every 
night is a show stopper. Once there is a release candidate I can create a new 
installer for you or Erich to put on the main page. 

Von meinen Macbook gesendet

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 15.09.2018 um 22:27 schrieb Rick McGuire :
> 
> 
> 
> On Sat, Sep 15, 2018 at 4:18 PM P.O. Jonsson  > wrote:
> Dear Rick,
> 
> For the record there IS an installer for MAC, since a long time. It is a 
> proper pkg installer. There are further variants as well, including the 
> version that can run without admin rights from a USB Stick. Link is on the 
> source forge site.
> 
> For the record *you* have a Mac installer, the oorexx project does not have 
> an installer. An installer maintained by a third party that is not integrated 
> into our cmake build process does not count. Someone needs to step on and do 
> that integration. 
> 
> Rick
>   
> 
> https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 
> 
> 
> Any feedback as to what is considered to be missing most welcome.
> 
> I will try to make test cases for all example files in the coming weeks.
> 
> Given that version 5 of ooRexx is REALLY GREAT I think it should make it to 
> at least a release candidate. Anything not in can wait to 5.1.
> 
> Von meinen Macbook gesendet
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 15.09.2018 um 15:14 schrieb Rick McGuire > >:
>> 
>> 
>> 
>> On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher > > wrote:
>> Two quick questions:
>> what is the current state of the ooRexx interpreter in the trunk: does it 
>> have all the garbage collection enhancements applied already?
>> This has already be integrated.  
>> what is the state of ooRexx 5.0 beta: when will it be released (companies 
>> and organisations won't usually install software dubbed/in the state of 
>> "beta")?
>> There are still a couple of features that need docs and tests written, plus 
>> we still don't have a Mac installer.  It will be released when it is 
>> released. The same answer you get every time you ask this question. If you 
>> wish it to be done faster, then pitch in with completing the remaining work.
>> 
>> Rick 
>>  
>> ---rony
>> 
>> ___
>> 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 
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rick McGuire]

On Sat, Sep 15, 2018 at 4:18 PM P.O. Jonsson  wrote:

> Dear Rick,
>
> For the record there IS an installer for MAC, since a long time. It is a
> proper pkg installer. There are further variants as well, including the
> version that can run without admin rights from a USB Stick. Link is on the
> source forge site.
>

For the record *you* have a Mac installer, the oorexx project does not have
an installer. An installer maintained by a third party that is not
integrated into our cmake build process does not count. Someone needs to
step on and do that integration.

Rick


>
> https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0
>
> Any feedback as to what is considered to be missing most welcome.
>
> I will try to make test cases for all example files in the coming weeks.
>
> Given that version 5 of ooRexx is REALLY GREAT I think it should make it
> to at least a release candidate. Anything not in can wait to 5.1.
>
> Von meinen Macbook gesendet
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 15.09.2018 um 15:14 schrieb Rick McGuire :
>
>
>
> On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher 
> wrote:
>
>> Two quick questions:
>>
>>- what is the current state of the ooRexx interpreter in the trunk:
>>does it have all the garbage collection enhancements applied already?
>>
>> This has already be integrated.
>
>>
>>- what is the state of ooRexx 5.0 beta: when will it be released
>>(companies and organisations won't usually install software dubbed/in the
>>state of "beta")?
>>
>> There are still a couple of features that need docs and tests written,
> plus we still don't have a Mac installer.  It will be released when it is
> released. The same answer you get every time you ask this question. If you
> wish it to be done faster, then pitch in with completing the remaining work.
>
> Rick
>
>
>>
>>-
>>
>> ---rony
>>
>> ___
>> 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
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[P.O. Jonsson]

Dear Rick,

For the record there IS an installer for MAC, since a long time. It is a proper 
pkg installer. There are further variants as well, including the version that 
can run without admin rights from a USB Stick. Link is on the source forge site.

https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 


Any feedback as to what is considered to be missing most welcome.

I will try to make test cases for all example files in the coming weeks.

Given that version 5 of ooRexx is REALLY GREAT I think it should make it to at 
least a release candidate. Anything not in can wait to 5.1.

Von meinen Macbook gesendet

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 15.09.2018 um 15:14 schrieb Rick McGuire :
> 
> 
> 
> On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher  > wrote:
> Two quick questions:
> what is the current state of the ooRexx interpreter in the trunk: does it 
> have all the garbage collection enhancements applied already?
> This has already be integrated.  
> what is the state of ooRexx 5.0 beta: when will it be released (companies and 
> organisations won't usually install software dubbed/in the state of "beta")?
> There are still a couple of features that need docs and tests written, plus 
> we still don't have a Mac installer.  It will be released when it is 
> released. The same answer you get every time you ask this question. If you 
> wish it to be done faster, then pitch in with completing the remaining work.
> 
> Rick 
>  
> ---rony
> 
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rick McGuire]

On Fri, Sep 14, 2018 at 9:48 AM Rony G. Flatscher 
wrote:

> Two quick questions:
>
>- what is the current state of the ooRexx interpreter in the trunk:
>does it have all the garbage collection enhancements applied already?
>
> This has already be integrated.

>
>- what is the state of ooRexx 5.0 beta: when will it be released
>(companies and organisations won't usually install software dubbed/in the
>state of "beta")?
>
> There are still a couple of features that need docs and tests written,
plus we still don't have a Mac installer.  It will be released when it is
released. The same answer you get every time you ask this question. If you
wish it to be done faster, then pitch in with completing the remaining work.

Rick


>
>-
>
> ---rony
>
> ___
> 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] Current state ad memory enhancements, state of ooRexx 5.0 beta?

[Rony G. Flatscher]

Two quick questions:

  * what is the current state of the ooRexx interpreter in the trunk: does it 
have all the garbage
collection enhancements applied already?
  * what is the state of ooRexx 5.0 beta: when will it be released (companies 
and organisations
won't usually install software dubbed/in the state of "beta")?

---rony

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