Re: [Oorexx-devel] Sandbox

On 22.04.2024 18:02, ooRexx wrote: On 22. Apr 2024, at 16:54, Rony G. Flatscher wrote: On 22.04.2024 15:24, ooRexx wrote: ... cut ... AFAICT these are meant to initially match the release versions. In the case that minor changes are applied to a released version and a minor release

Re: [Oorexx-devel] Sandbox

On 22.04.2024 17:06, ooRexx wrote: On 22. Apr 2024, at 16:54, Rony G. Flatscher wrote: On 22.04.2024 15:24, ooRexx wrote: is it ok to branch off and create folders in the Sandbox branch? A "sandbox" is an area where experiments can be carried out. In the ooRe

Re: [Oorexx-devel] Sandbox

On 22.04.2024 15:24, ooRexx wrote: is it ok to branch off and create folders in the Sandbox branch? A "sandbox" is an area where experiments can be carried out. In the ooRexx project there are subdirectories by the name of the developers, committers, such that one can use one own's temporary

Re: [Oorexx-devel] Question ad tracing the invocation of a method containing a reply statement

Committed with [r12834] <https://sourceforge.net/p/oorexx/code-0/12834/> (code) and [r12835] <https://sourceforge.net/p/oorexx/code-0/12835/> (unit tests) after running the entire test suite. ---rony On 21.04.2024 20:47, Rony G. Flatscher wrote: Thinking about this probl

Re: [Oorexx-devel] Question ad tracing the invocation of a method containing a reply statement

re reply ... 8 *-1* reply *I2> Method "TEST_REPLY" with scope "TEST" in package "G:\test\orx\trace\test_reply.rex". 9 *-2* say "after reply ..." after reply ... *As can be seen the invocation enter and exit tracelines

Re: [Oorexx-devel] ooRexx website

Terry, that is *great* that you have been able to overhaul it, thank you very much! ---rony On 20.04.2024 02:05, taf wrote: Well, nevermind Just found svn info and I think I've got what I need. On 2024.04.19 09.04, taf wrote: Hello all, I've finally gotten started on the website.  I'm

[Oorexx-devel] Question ad tracing the invocation of a method containing a reply statement

Given the following program: .traceObject~option="T" -- from now on display thread id in prefix t=.test~new t~test_reply ::class test ::method test_reply say "before reply ..." reply say "after reply ..." ::options trace all Running it will yield:

Re: [Oorexx-devel] Preparing for the next release

Hi P.O., thank you for your information and efforts! How about targeting an initiative to create a new release (5.1.0) at the beginning of June then? Cheers ---rony On 19.04.2024 19:01, ooRexx wrote: A progress report on my activites today. The test was partially successful, if you look

Re: [Oorexx-devel] Test in environmentEntries.testGroup in error (Re: Planning to commit the enclosed diff for the trace invocation exit traceline

Changed the test to expect the NOMETHOD condition, cf. [r12830] (https://sourceforge.net/p/oorexx/code-0/12830/). ---rony On 11.04.2024 13:33, Rony G. Flatscher wrote: Hmm, there is one unexpected error in the test suite: [error] 20240411 11:35:15.207000 Test

Re: [Oorexx-devel] Planning to commit the enclosed diff for the trace invocation exit traceline

0/> (test units). ---rony On 11.04.2024 11:53, Rony G. Flatscher wrote: Enclosed please find the diff for adding the trace invocation exit traceline to complement the trace invocation (>I>) traceline. The reason is mainly to make sure that the changes are sensible and acceptable.

[Oorexx-devel] Test in environmentEntries.testGroup in error (Re: Planning to commit the enclosed diff for the trace invocation exit traceline

trace r*trace n -- <-- this line # 103* Not sure whyt it does not trigger 97.1 as the other tests in this test unit do. Will be able to adjust this test to not bring up an error, but before doing so the question, why that would be the case? Why would the changes for the trace invocation exit

[Oorexx-devel] Planning to commit the enclosed diff for the trace invocation exit traceline

Enclosed please find the diff for adding the trace invocation exit traceline to complement the trace invocation (>I>) traceline. The reason is mainly to make sure that the changes are sensible and acceptable. While working on this I noticed that in RexxActivation.cpp there is a superfluous

Re: [Oorexx-devel] An example run (Re: One more trace entry for exiting a routine or method with a trace prefix of

ram with internal routines (indicated by a label, i.e. an identifier followed by a colon) which may get signaled or called. Trace label will trace those labels.—-rony On 4/10/2024 7:40 AM, Rony G. Flatscher wrote: Here an example program that uses a routine and met

[Oorexx-devel] An example run (Re: One more trace entry for exiting a routine or method with a trace prefix of

Here an example program that uses a routine and methods (and internal routines) for getting an impression on the trace output: say "hi" o=.test~new say "o~hi :" o~hi say "o~ho :" o~ho say "pp(abc):" pp(abc) ::routine pp res=br(arg(1)) return res br: return "[" || arg(1) || "]" ::class

[Oorexx-devel] One more trace entry for exiting a routine or method with a trace prefix of

In ooRexx there is an interesting trace line that informs when a routine or method is entered. "2.29.5. The Format of Trace Output" reads: >I> Identifies an entry to a routine or method. This trace entry will only appear if tracing is enabled using the ::OPTIONS directive using TRACE

Re: [Oorexx-devel] Working with TraceObjects, maybe adding OBJECT, removing OBJECTID, and adding STACKFRAME?

On 03.04.2024 09:26, Chip Davis wrote: Seems more Rexx-ish, unless its specification might conflict with a future usage of the term in that context. -Chip- On 4/2/2024 4:19 PM, Rony wrote: Another question: offline I got the suggestion to change the NR entry in TraceObject to NUMBER. What do

Re: [Oorexx-devel] Update with further information ... (Re: Anyone with a more uptodate debugger? (Re: Segmentation faults in environmentEntries.testGroup

! Will commit the changes to trunk shortly. ---rony P.S.: As setMethod/unsetMethod are documented they will get used in the wild such that we should attempt to remove the root cause eventually. On Fri, Apr 5, 2024 at 8:26 AM Rony G. Flatscher wrote: Thankfully Jean Louis was able

[Oorexx-devel] Update with further information ... (Re: Anyone with a more uptodate debugger? (Re: Segmentation faults in environmentEntries.testGroup

case gets applied to a class object * TraceObject subclasses StringTable which in native code subclasses StringHashCollection On 04.04.2024 19:04, Rony G. Flatscher wrote: Am using an almost ten year old version of MVS (Microsfot Visual Studio), which was bought (but due to lack of money h

Re: [Oorexx-devel] Anyone with a more uptodate debugger? (Re: Segmentation faults in environmentEntries.testGroup

a private message just now. thank you very much! Best regards ---rony Am 04.04.2024 um 19:04 schrieb Rony G. Flatscher : Am using an almost ten year old version of MVS (Microsfot Visual Studio), which was bought (but due to lack of money has not been updated by buying an update, newer

[Oorexx-devel] Anyone with a more uptodate debugger? (Re: Segmentation faults in environmentEntries.testGroup

elp highly appreciated! ---rony On 03.04.2024 17:29, Rony G. Flatscher wrote: On 03.04.2024 16:25, ooRexx wrote: It seems we currently have ALL platforms failing this test, can the person (Rony?) who committed lately check if there was a side-effect of the changes and/or amend the

Re: [Oorexx-devel] Segmentation faults in environmentEntries.testGroup

Hi P.O., On 03.04.2024 17:33, ooRexx wrote: I was imprecise: all Linux/Unix/macOS platforms have a segmentation fault in that group, the test itself is not failing, but the cause of the segfault must be found and my guess is that it is in one of your commits? No, not directly. As for the

Re: [Oorexx-devel] Segmentation faults in environmentEntries.testGroup

On 03.04.2024 16:25, ooRexx wrote: It seems we currently have ALL platforms failing this test, can the person (Rony?) who committed lately check if there was a side-effect of the changes and/or amend the test to the new behaviour. Executing

Re: [Oorexx-devel] Working with TraceObjects, maybe adding OBJECT, removing OBJECTID, and adding STACKFRAME?

After making sure that TEST.testgroup and TEST_TestObject.testgroup work, I committed  12814 (code) and 12815 (doc) to see whether all tests keep on running on all platforms via Jenkins. ---rony On 29.03.2024 15:43, Rony G. Flatscher wrote: While experimenting with TraceObjects for anaylsis

[Oorexx-devel] Working with TraceObjects, maybe adding OBJECT, removing OBJECTID, and adding STACKFRAME?

While experimenting with TraceObjects for anaylsis it seems that the following would be an improvement: * replace the OBJECTID entry with an OBJECT entry, storing the receiver/self object: if needing the identity hash value (e.g. for externalization) one can send it the identityHash

[Oorexx-devel] Work concluded (Re: Not quite (Re: RFE # 825: work concluded

suite and b) the RexxLA Jenkins build system are instrumental and extremely helpful for the ooRexx project! ---rony On 27.03.2024 16:02, Rony G. Flatscher wrote: There were two new entries, docs and tests need to be supplied, hence reopened. ---rony On 26.03.2024 15:53, Rony G. Flatscher wrote:

[Oorexx-devel] Not quite (Re: RFE # 825: work concluded

There were two new entries, docs and tests need to be supplied, hence reopened. ---rony On 26.03.2024 15:53, Rony G. Flatscher wrote: A few minutes ago I committed the test cases for <<https://sourceforge.net/p/oorexx/feature-requests/825/> was updated:> ("TraceObject&q

Re: [Oorexx-devel] Method's "scope" method and TRACE's ">I>" information

Added entries OBJECTID and SCOPE with [r12808]. ---rony On 27.03.2024 14:47, Rony G. Flatscher wrote: On 27.03.2024 14:26, Rick McGuire wrote: I also want to point out this was something I pointed out previously when I said that the lock count was not a very useful piece of information

Re: [Oorexx-devel] Method's "scope" method and TRACE's ">I>" information

On 27.03.2024 14:38, Rick McGuire wrote: On Wed, Mar 27, 2024 at 9:33 AM Rony G. Flatscher wrote: On 27.03.2024 14:16, Rick McGuire wrote: The scope is not the variable pool that is used, it is rather the index used to look up the appropriate variable pool in the object

Re: [Oorexx-devel] Method's "scope" method and TRACE's ">I>" information

rhaps the identity hash)" + "method scope (to identify the variable pool in question)" + "the lock count for the activity". That will uniquely identify what the scope lock situation is. How about an entry OBJECTID with the identity hash as a value? ---rony On Wed,

Re: [Oorexx-devel] Method's "scope" method and TRACE's ">I>" information

2024 at 9:10 AM Rony G. Flatscher wrote: Consider the following short program that defines a class and an instance method and uses them: .TraceObject~option='N' .test~clzHi-- class method will be invoked .test~new~hi -- instance method will be invoked

[Oorexx-devel] Method's "scope" method and TRACE's ">I>" information

Consider the following short program that defines a class and an instance method and uses them: .TraceObject~option='N' .test~clzHi-- class method will be invoked .test~new~hi -- instance method will be invoked ::class test ::method clzHi class say self": clzHi,

[Oorexx-devel] Announcing Release of the ooRexx-Java external function package "BSF4ooRexx850"

At this year's International Rexx Symposium (https://www.rexxla.org/events/schedule.rsp?year=2024) BSF4ooRexx850, a bidirectional ooRexx-Java bridge, got released as "GA" (general available). The most notable changes got presented at that very symposium and the slides of the additions and

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

Hi Erico, On 26.03.2024 19:39, Erico Mendonca via Oorexx-devel wrote: Not entirely related, but if you guys want to automate some builds, consider using Open Build Service (just call the API, even from Jenkins). Here's an example:

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

has pointed out (see below)? Would anyone have any suggestions, ideas, takers? ---rony On 30.11.2023 08:56, Rony G. Flatscher wrote: Hi Gil, thank you very much! On 29.11.2023 19:10, Gilbert Barmwater wrote: I guess I need to refresh everyone's memory on this topic. When we released 5.

[Oorexx-devel] RFE # 825: work concluded

A few minutes ago I committed the test cases for < was updated:> ("TraceObject") which concludes the work. ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] Updated rexxref and rexxpg books (Re: Wow! (Re: Documentation added to rexxref (Re: Ad debugging multithreaded programs, updated RFE # 825

. Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se Am 25.03.2024 um 14:00 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:Having received direct feedback from Josep Maria and having had some time to also work on rexxpg (there is an overview of the available ooRexx classes) the c

[Oorexx-devel] Updated rexxref and rexxpg books (Re: Wow! (Re: Documentation added to rexxref (Re: Ad debugging multithreaded programs, updated RFE # 825

Having received direct feedback from Josep Maria and having had some time to also work on rexxpg (there is an overview of the available ooRexx classes) the commits [r12804] and [r12805] should trigger Jenkins to automatically create the two books sometimes in the next few hours. It would be

Re: [Oorexx-devel] Ad "scope": how to discover it at runtime?

it. ---rony On 24.03.2024 15:58, Rony G. Flatscher wrote: On 24.03.2024 15:48, Rick McGuire wrote: if .context~executable~isa(.Method) then say .context~executable~scope Wow, thank you very much for this pointer! (I was not aware of the Method class allowing for retrieving it, which is really great

Re: [Oorexx-devel] Wow! (Re: Documentation added to rexxref (Re: Ad debugging multithreaded programs, updated RFE # 825

On 24.03.2024 15:48, P.O. Jonsson wrote: And WOW what a humongous piece of work not just implementing it but actually DOCUMENTING it! Hat´s off. :) (Indeed time is a big problem, always. The test cases need to be done, which is next on my TODO list.) ---rony

Re: [Oorexx-devel] Ad "scope": how to discover it at runtime?

method to the new documentation in the next days (after waiting a bit for any feedback). ---rony On Sun, Mar 24, 2024 at 10:32 AM Rony G. Flatscher wrote: While working on the multithreaded related parts it has become clear that the term "scope" is very important, s

[Oorexx-devel] Wow! (Re: Documentation added to rexxref (Re: Ad debugging multithreaded programs, updated RFE # 825

*Wow*, that was fast, the rendered PDF and HTML version is already online! ---rony On 24.03.2024 14:52, Rony G. Flatscher wrote: Writing up the documentation for the new TraceObject class and the new subchapter for debugging multithreaded programs has turned out to be quite a hefty piece

[Oorexx-devel] Ad "scope": how to discover it at runtime?

While working on the multithreaded related parts it has become clear that the term "scope" is very important, such that I linked the word "scope" to the respective section that describes it. Also, looking at questions and answers in the RexxLA mailing list related to multithreading "scope"

[Oorexx-devel] Documentation: ad "rr" and extracting svg from xhtml files with (docs\trunktools\RailRoadDiagrams\extract_svg_from_rr_xhtml.rex)

The program "docs\trunktools\RailRoadDiagrams\extract_svg_from_rr_xhtml.rex" got changed in the past weeks a little bit: - 20240316: changed the svg name needle from 'Background: some of the xhtml files had Unix LF, some Windows CR-LF. Extracting the svg data causes svn problems at

[Oorexx-devel] Documentation added to rexxref (Re: Ad debugging multithreaded programs, updated RFE # 825

Writing up the documentation for the new TraceObject class and the new subchapter for debugging multithreaded programs has turned out to be quite a hefty piece of work despite having already the raw text available (and adhering to it). In the end, the rexxref sections that play a role in

Re: [Oorexx-devel] Ad debugging multithreaded programs, updated RFE # 825

ring prepends it with the letter L it should read: "HASSCOPELOCK" .true/.false, makeString uses an asterisk, if .true, a blank character else (cf. "4.2.2. Scope") "SCOPELOCKCOUNT"   a number, makeString prepends it with the letter L (cf. "4.2.2. Sc

Re: [Oorexx-devel] Question ad solution for two trace related tests failing in trace exits

to change anything in the native code. ---rony On 13.03.2024 19:21, Rony G. Flatscher wrote: There are two trace related tests in the test suite failing (all other pass): [failure] 20240313 18:16:37.50   Test:   TESTIOEXITTRACE   Class:  RexxStart.testGroup   File: ...\oorexx

[Oorexx-devel] Question ad solution for two trace related tests failing in trace exits

There are two trace related tests in the test suite failing (all other pass): [failure] 20240313 18:16:37.50   Test:   TESTIOEXITTRACE   Class:  RexxStart.testGroup   File: ...\oorexx\test\trunk\ooRexx\API\oo\ProcessRexxStart.testGroup   Line:   244   Failed:

Re: [Oorexx-devel] A crash in the test suite

Interestingly, creating a DEBUG version and using the testbinaries of it does not cause the crash. ---rony On 12.03.2024 16:47, Rony G. Flatscher wrote: Will create a debug version of ooRexx with my version of the MS compiler and rerun the testsuite to see whether that makes a difference

Re: [Oorexx-devel] A crash in the test suite

Will create a debug version of ooRexx with my version of the MS compiler and rerun the testsuite to see whether that makes a difference (used Open Object Rexx Version 5.1.0 r12787, Build date: Feb 12 2024 from SourceForge with a privately built version of the testbinaries). ---rony

Re: [Oorexx-devel] A crash in the test suite

Here the screenshots: followed by: Then the location already reported in the previous mail will be shown again. ---rony On 12.03.2024 16:28, Rony G. Flatscher wrote: While running the testsuite on Windoes with "testOORexx.rex" from test/trunk a heap related crash occurs in the

[Oorexx-devel] A crash in the test suite

While running the testsuite on Windoes with "testOORexx.rex" from test/trunk a heap related crash occurs in the testbinary named orxclassic.cpp at line # 290: nextblock = currentblock->shvnext; Here the call stack: > orxclassic.dll!TestFVariablePool_impl(RexxCallContext_ *

[Oorexx-devel] Ad debugging multithreaded programs, updated RFE # 825

was updated: Taking into account the discussions on the developer list of the last months and years, an implementation got created that reflects the comments (no environment variable, not forcing Rexx programmers to either or trace

[Oorexx-devel] Fwd: Brief explanations on ooRexx' multithreading capabilities and the desired sample outputs (Re: Mike's suggestion added (Re: Another updated version for testing (Re: An updated versi

On 06.02.2024 18:03, Mike Cowlishaw wrote: Nice, thanks!! +1 You can probably guess which one, showing threads, that I prefer :-)) :)) The nice thing about this IMHO is the freedom for the Rexx programmer to choose the best formatting for the problem. Use the standard, use the verision

Re: [Oorexx-devel] Mike's suggestion added (Re: Another updated version for testing (Re: An updated version available (Re: Ad debugging multithreaded programs, a working test version

There is a new version to * incorporate Mike's suggestion of inserting the thread number into the trace prefix after the second character, the option is 'T' (for thread), * a new (artificial) program that creates many threads such that the different formats can be compared

[Oorexx-devel] Mike's suggestion added (Re: Another updated version for testing (Re: An updated version available (Re: Ad debugging multithreaded programs, a working test version

x~right(1) return line prefixT rest ---rony P.S.: got already the updated version such that you can download and experiment for yourself (and with your own Rexx programs). On 04.02.2024 16:48, Rony G. Flatscher wrote: There is a new version available at , which is regarded to be

[Oorexx-devel] Another updated version for testing (Re: An updated version available (Re: Ad debugging multithreaded programs, a working test version

There is a new version available at , which is regarded to be the final version for the time being. The web page allows for downloading a portable 64-bit Windows debug version of ooRexx 5.1.0beta that implements the TraceObject class which gets used by the Rexx scripts stored in the

Re: [Oorexx-devel] An updated version available (Re: Ad debugging multithreaded programs, a working test version

There is a new version available at , which is regarded to be the final version. Some changes: * make traceLine align in S and F mode if object related information is not present * start work on traceutils.cls meant to get TraceObject related utilities, e.g. "toJSON()" and "toCSV()"

[Oorexx-devel] An updated version available (Re: Ad debugging multithreaded programs, a working test version

There is an updated version of the implementation and build available at . Here the changes: * adding the class attribute COUNTER to TraceObject * adding an entry NR (creation sequence number) in TraceObject, allowing to exactly determine the

Re: [Oorexx-devel] Ad debugging multithreaded programs, a working test version

On 29.01.2024 11:04, P.O. Jonsson wrote: Am 28.01.2024 um 17:32 schrieb Rony G. Flatscher : The creation of the working test version has costed me already much more time than budgeted. Are you aware of any software project that didn’t ? ;-) You forgot the Pi factor* * „Every project

Re: [Oorexx-devel] Ad debugging multithreaded programs, a working test version

Dear P.O., On 28.01.2024 17:22, P.O. Jonsson wrote: An obvious candidate for testing this might be the test framework for ooRexx. When running the tests on Windows (7,8,10,11) it invariably gets stuck at the very end (after a successful test run ) suggesting a dangling/blocked process

[Oorexx-devel] Ad debugging multithreaded programs, a working test version

At you will find a portable ooRexx debug version for Windows that includes a test version of the suggested multithreaded trace, implemented in a way that adheres to Rick's idea, such that a Rexx programmer can freely format traces as he or she

[Oorexx-devel] Ad debugging multithreaded programs: suggesting a few minor changes

While experimenting with the trace infos I think we should choose the names for the entries in the TraceObject in a self-documentary manner, such that Rexx users can intuitively understand their meaning (saving looking up the documentation once accustomed). Suggesting to use the following

Re: [Oorexx-devel] A problem at link time for rexx.dll (Re: RexxDateTime is internal, how to use its information for a .DateTime object to be stored in a StringTable?

O.K. found the (rookie) error: although defined in TraceObjectClass.hpp it did not get implemented and initialized in TraceObjectClass.cpp. :( Still hitting problems later on that probably have to do with my manual editing and doing something wrong somewhere, so starting out with a pristine

[Oorexx-devel] A problem at link time for rexx.dll (Re: RexxDateTime is internal, how to use its information for a .DateTime object to be stored in a StringTable?

pp M runtime/InterpreterInstance.cpp M runtime/InterpreterInstance.hpp M runtime/RexxCore.h How could I possibly fix this? ---rony P.S.: I can supply all the changes (or for specific files) as a "svn diff" of course, if that would help better.

Re: [Oorexx-devel] RexxDateTime is internal, how to use its information for a .DateTime object to be stored in a StringTable?

Ah, think I found a solution by using TheRexxPackage->findClass(). ---rony On 25.01.2024 14:51, Rony G. Flatscher wrote: Experimenting with tracing and one idea that came up with was to also supply Activation::getTime()  which is an internal interpreter/classes/support/RexxDateTime obj

[Oorexx-devel] RexxDateTime is internal, how to use its information for a .DateTime object to be stored in a StringTable?

Experimenting with tracing and one idea that came up with was to also supply Activation::getTime()  which is an internal interpreter/classes/support/RexxDateTime object and as such cannot be used directly as an argument to put(). The attempt is to create a TIMESTAMP entry in a StringTable

Re: [Oorexx-devel] An ooRexx implementation of the TraceObject class

g/waiting (indicating a method currently guarded and waiting on the object's lock). This would ease analyzing the trace log considerably, if interested to find the blocked statements in a multithreaded program in case of deadlocks. ---rony On Mon, Jan 22, 2024 at 11:32 AM Rony G. Flatscher

[Oorexx-devel] An ooRexx implementation of the TraceObject class

Here an ooRexx implementation of the proposed TraceObject class in today's "Proposal for multithreaded trace prefix" class: /* = */ ::class "TraceObject" subclass StringTable public /*

[Oorexx-devel] Proposal for multithread trace prefix

This proposal attempts to meet with the discussions that have been taking place in the past years regarding supplying multithreaded related trace information to regular trace. In the following the multithreaded related trace information is referred to as "mtPrefix" (multithreaded prefix) meant

[Oorexx-devel] Draft: documentation for multithreaded trace prefix (mtPrefix)

As suggested by Rick in the past here as a first step a draft for adding documentation to the ooRexx reference such that it becomes possible to communicate about the multithreaded trace prefix and its meaning. Starting out with the current documentation the nomenclatura is kept the same,

[Oorexx-devel] Question ad multithreading (blocked threads)

Multithreading is a very powerful feature of ooRexx and very versatile! For the following two scenarios I would have a question ad how to determine in native code whether a method routine is currently executing guarded or unguarded and whether it is currently blocked (waiting on a lock and if

Re: [Oorexx-devel] Universal package and rexx.img

Dear P.O., On 15.01.2024 20:51, oorexx wrote: I wanted to split the macOS installer and have prepared 2 new jobs. I have disabled ooRexx-macOS12-build and created ooRexx-macOS12-X86_64-build and ooRexx-macOS12-ARM64-build. ... cut ... (looks o.k. to me :) ) ... cut ... Finally we have to

Re: [Oorexx-devel] rexxGTK build

Hi Greetz, that is *quite* impressive! Would you consider giving a presentation at this year's Rexx symposium about it? Cheers ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] A thought on multi-threaded tracing.

DebugInfo", "Supplemental", "Glimpse". The latter two are not intuitive, but their first letter are not in use. "DebugInfo" would not hint at the purpose of helping to trace multithreaded execution of programs. On 30.09.2023 14:18, Rony G. Flatscher wrote:

[Oorexx-devel] Universal package and rexx.img

As rexx.img must be of the same architecture, bitness and endianness it is not possible to use a single rexx.img for different architectures, bitnesses and endiannesses. The present packaging and installation of ooRexx can therefore not take advantage of universal packages available on macOS

[Oorexx-devel] Announcing new beta of BSF4ooRexx850 (a very easy to use Rexx/ooRexx - Java bridge)

Since a few minutes there is a new beta version of BSF4ooRexx850 available from Sourceforge. If no show-stopper errors get reported then this version will get released by this year's International Rexx symposium at the beginning of March in the area auf Brisbane, Australia (consider to offer a

Re: [Oorexx-devel] Question ad rexx.img

On 07.01.2024 20:00, Rick McGuire wrote: On Sun, Jan 7, 2024 at 1:21 PM Rony G. Flatscher wrote: Is rexx.img dependent on the architecture and bitness? Yes, it contains LOTS of binary data that depends on the bitness of the architecture. There are some bits that might even

[Oorexx-devel] Question ad rexx.img

Is rexx.img dependent on the architecture and bitness? With other words: can a rexx.img be used at the same time for arm64 and amd64 (Intel)? ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] Documentation build process amended

On 01.01.2024 12:50, ooRexx wrote: Forst of all I want to wish everybody a (late) happy new year and a good continuation of 2024! Me too to everyone! With the kind help of Gil the documentation build service on Jenkins have been amended to reflect the correct date & revision information for

[Oorexx-devel] Request for fixing crash reported in bug item #1872

Since last August a crash got reported in which can be easily reproduced by following the directions there. Using the supplied simple C++-only program will work flawlessly if invoked simply as testTerminate.exe it will run flawlessly using 250

Re: [Oorexx-devel] OORexx 5.0 builds

Hi Erico, On 21.12.2023 18:27, Erico Mendonca via Oorexx-devel wrote: In case anyone is interested, I reactivated and updated some automated Linux builds for OORexx 5.0 on OpenSUSE Build Service: https://build.opensuse.org/package/show/home:emendonca:oorexx/oorexx5 Great! Clicking on the

[Oorexx-devel] oelinfo from sandbox added to samples/ole/oleinfo (Re: Planned additions, release of ooRexx 5.1 ?

be seen at: <http://sourceforge.net/p/oorexx/code-0/12746> Changed the license in all files, updated readme.txt and test.rex (cater for Internet Explorer being pulled from Windows eventually) accordingly. ---rony On 20.11.2023 11:30, Rony G. Flatscher wrote: Given some free time I

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

for you or for anyone else on this list to give a helping hand? The more shoulders carry this load the easier for each individual and the faster can the clean up go? (Personally, I will probably only be able to get enough free time again during the New Year vacation and would like to focus on the &q

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

Hi Michael, AFAIK nothing has happened since then. Would you be interested in taking this on? Cheers ---rony On 24.11.2023 01:43, Michael Lueck wrote: Greetings ooRexx team, Reminder of Rick's prior email... Begin Forwarded Message Subject: [Oorexx-devel] I think

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

  There has been a good amount of work on this but I'd really want to see ALL of them completed. Thanks! Could you point them out (unfortunately, I have no idea what you mean or which bugs and RFEs are affected)? ---rony On 11/23/2023 3:51 PM, Rony G Flatscher wrote: Dear P.O., fine, arou

Re: [Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

release I have a tight schedule from now until Christmas so a release in 2023 would be very hard for me to cope with. What about aiming for end of January? Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se Am 20.11.2023 um 11:30 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac

[Oorexx-devel] Planned additions, release of ooRexx 5.1 ?

Given some free time I would like to add the following things to ooRexx 5.1: * the Windows oleinfo Rexx utilities from the sandbox (https://sourceforge.net/p/oorexx/code-0/HEAD/tree/sandbox/rony/oleinfo/) o planned for being placed as is in a new directory ooRexx/samples/ole/oleinfo

[Oorexx-devel] An observation (hang in SystemsCommands.cpp, sometimes crash)

(This is using Microsoft Windows [Version 10.0.19045.3570], Open Object Rexx Version 5.1.0 r12722 - Internal Test Version, Java openjdk version "17.0.6" 2023-01-17 LTS). But can be observed also on other Java versions, older or newer.) This has been a phenomenon for quite some time: sometimes

Re: [Oorexx-devel] Jenkins

Gil, On 27.10.2023 17:19, Gilbert Barmwater wrote: Glad to see that you are back "in the saddle" so to speak!  Rony and I have been working off-list to implement a mechanism to automate the updating of the information in the "Edition" of each book.  I have done the change in the ooRexx version

[Oorexx-devel] Question ad Rexx interpreter instances

Is there a way to find out whether a particular Rexx instance is being used for an activity, and if so how? Background: as long as it is not possible to safely terminate a Rexx interpreter instance I might be inclined to create a pool of Rexx interpreter instances and rather than terminating

Re: [Oorexx-devel] A thought on multi-threaded tracing.

Time passes too quickly. @Rick: do you have any intentions to implement the ideas you have communicated? ---rony On 25.03.2023 16:58, Rick McGuire wrote: On Sat, Mar 25, 2023 at 11:52 AM Gilbert Barmwater wrote: Let me see if I've got this.  If there was a class, perhaps a subclass

Re: [Oorexx-devel] Committing change

+1 ---rony On 22.09.2023 22:26, René Jansen wrote: +1 On 22 Sep 2023, at 19:55, Sahananda Sahananda wrote: Hi Terry, It looks like you are not a committer.  I believe that Erich as the project manager could convey that right on you.  In the old days that would follow a poll of all the

Re: [Oorexx-devel] oorexx.org lists 4.2.0 as current release for downloads

Dear Jon: On 17.09.2023 18:53, Sahananda Sahananda wrote: I notice that https://www.oorexx.org/download.html shows 4.2.0 as our latest release. :-(  believe the website is source controlled through the SVN and I find the page source in the SVN at  / websites / main / trunk / docroot /

Re: [Oorexx-devel] ooRexx access to Google Sheets

Hi Sandy, On 07.09.2023 17:39, Sanford Geiger wrote: *Is there an ooRexx example of using rexxcurl with the JSON class? * As the command curl is now available on Windows as well (it has been available on the Unix operating systems for a long while), here a program that uses the curl command

Re: [Oorexx-devel] ooRexx documentation build

Hi P.O., first of all thank you very much for all of your efforts in midst of your vacation far away from your IT infrastructure! --- One problem is probably that we have not done another release since the last time where we had quite a few new scripts built to support the release process.

Re: [Oorexx-devel] ooRexx documentation for 5.10 beta ?

On 15.08.2023 17:46, Rony G. Flatscher wrote: Using the latest 64-bit version of ooRexx (oorexx-5.1.0-12718.windows.x86_64.exe) I noticed that Jean Louis' commits to the documentation [r12715] for his enhancements to the WindowsClipboard class is not reflected in the documentation that gets

[Oorexx-devel] ooRexx documentation for 5.10 beta ?

Using the latest 64-bit version of ooRexx (oorexx-5.1.0-12718.windows.x86_64.exe) I noticed that Jean Louis' commits to the documentation [r12715] for his enhancements to the WindowsClipboard class is not reflected in the documentation that gets installed with r12718! Instead it seems that the

Re: [Oorexx-devel] #1909 Error building oorexx 5.1.0 build 12694 from source

Dear P.O., On 26.06.2023 10:48, P.O. Jonsson wrote: I intend to commit this change in the coming days, are there any objections? Sideffects? being side-tracked for other things and probably anyone else too, it would be great if you could take on these important changes! Also, judging from

[Oorexx-devel] New beta of BSF4ooRexx850 available, version 850.20230621 (Re: [Bsf4oorexx-devel] Another (Re: [rexxla-members] New beta of BSF4ooRexx850 available, update focused on JDOR

1-250_windows_word_ole_clipboard.rxj ... MS Word: Windows only At this time BSF4ooRexx850 is regarded to be feature complete. There are no known bugs such that this version may be released as "general available" in the near future. ---rony On 12.06.2023 17:14, Rony G. Flatscher wrote: There i

Re: [Oorexx-devel] A thought on multi-threaded tracing.

Is there any news on this? As long as these thoughts of enhancements are missing in form of real code one cannot use them to debug mulit-threaded programs with the necessary context information. Therefore the question when any such changes can be expected? Or would it be better for the

  1   2   3   4   5   6   7   8   9   10   >