without a need to install them globally on your system. Since ooRexx 5.0 it is possible to have
different versions of ooRexx 5.0 and higher running in parallel on the same computer. Therefore, you
can use different versions of net-oo-rexx in parallel on the same computer, if need be.
It does no
t /in
parallel with the new version!/
BTW, the rexx-parser package from Josep Maria Blasco got updated as Josep Maria did a lot of work
there, great and interesting stuff! You can use his rexx-parser to parse any Rexx and ooRexx
program. One off-spring available in the rexx-parser package is the syn
u can already use ooRexx with BSF4ooRexx, or NetRexx.
One important package is "oorexxshell", which is a *great*, versatile, very useful shell for
Windows, MacOS, and LInux by Jean Louis Faucher.
See the enclosed "readme*txt" files for more information.
---rony
"net-
e Tomcat, IBM
WebSphere, or any other JavaEE/Jakarta web server offering, by using the ScriptTagLib library from
<https://sourceforge.net/projects/bsf4oorexx/files/Sandbox/rgf/taglibs/ga/>. (There is a recorded
presentation about this infrastructure from an ApacheCon presentation here:
<
test_reverse(1): 00:00:00.00 -> 00:00:00.00 per call
total duration : 00:00:00.035000
G:\test\orx\gc>test_gc_speed.rex
version: RELEASE
test_gc(1) : 00:00:00.036000 -> 00:00:00.07 per call (effective
calls: 5000)
test_reverse(1): 00:00:00.000000 -
rcised: docs [r13012], tests
[r13013], and code [r13014]. The above RFE-link has links to the commits and related RFEs.
Will monitor Jenkins and how the builds on the Jenkins hosted platforms do,
including the test suite.
---rony
___
Oorexx-devel m
test_gc(1) : 00:00:00.038000 -> 00:00:00.03 per call
test_reverse(1): 00:00:00.001000 -> 00:00:00.00 per call
total duration : 00:00:00.039000
---rony
On 30.08.2025 15:41, Rony G. Flatscher wrote:
This is the planned implementation of gc() which
* alwa
0 -> 00:00:00.00 per call
total duration : 00:00:00.991000
G:\test\orx\gc>rxenv rexx test_gc_speed.rex
test_gc(1) : 00:00:00.972000 -> 00:00:00.97 per call
test_reverse(1): 00:00:00.008000 -> 00:00:00.00 per call
total duration : 00:00:00.9
that are held in Rexx objects that have gone
out of scope)
* one should clearly document and warn about misusing this feature pointing
out at potential
runtime performance implications (like in other programming languages)
---rony
On 26.08.2025 22:28, Rony G. Flatscher wrote:
There is a
think? Any comments?
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
(e.g. for state changes, watching variables and the like).
This way the patch gets tested on all operating systems on Jenkins.
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo
Judging from the results on Jenkins this patch did not cause any failures, hence marking the
reported bug (https://sourceforge.net/p/oorexx/bugs/2030/) as being fixed.
---rony
On 24.08.2025 11:02, Rony G. Flatscher wrote:
On 23.08.2025 23:30, dominicjw...@gmail.com wrote:
Attached is the
.
Cheers
---rony
*From:*dominicjw...@gmail.com
*Sent:* 23 August 2025 21:49
*To:* 'Open Object Rexx Developer Mailing List'
*Subject:* RE: [Oorexx-devel] No, only the hang bug left and that can be solved with Dom Wise's
patch (Re: Maybe two different bugs? A question ad fixing
On 22.08.2025 21:58, Rony G. Flatscher wrote:
On 22.08.2025 13:31, Rony G. Flatscher wrote:
Having tested the interpreter without Dom's patch with the samples fxml_25, fxml_26, fxml_27, and
fxml_99 ("BSF4ooRexx850\samples\JavaFX") the following could be observed using differe
On 22.08.2025 13:31, Rony G. Flatscher wrote:
Having tested the interpreter without Dom's patch with the samples fxml_25, fxml_26, fxml_27, and
fxml_99 ("BSF4ooRexx850\samples\JavaFX") the following could be observed using different versions
of Java (Java 8 and in the end Java
ks to ooRexx (therefore the ObservableList is optimized for
JavaFX to cut down
callbacks)
* adding DatePicker adds callbacks each time a Cell ...
-----
I
ere side-effects in other parts, and if so,
which parts would need inspection, testing?
Any feedback, insights, ideas highly appreciated!
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
2-08-10. So I assume that with that beta version of ooRexx 5.0 the samples would ran.
However, there seem to have been occasionally problems on Windows (crash at termination) which could
be solved by adding "call sysSleep 0.01" right before exiting the Rexx program.
HTH
---rony
On 20.
from February, 23rd, 2023, so I assume it worked at that point in time. Yes,
there were problems earlier, however there were gone when Rick was working on the threading issues
reported back then.
HTH
---rony
*From:*Rony G. Flatscher
*Sent:* 18 August 2025 19:09
*To:* oorexx-devel
that on my machine I don’t get crashes running with the patch in *either*
location (i.e. including the one which crashes for Rony) so there might be some magic working just
for me and it might make no difference for anyone else but I’d definitely suggest trying with the
change ju
Dear Dom,
On 17.08.2025 17:31, dominicjw...@gmail.com wrote:
I am one such masochist that Rony was referring to 😊
Very glad that you are one! ;)
It seems that in InterpreterInstance::terminate() there can be situations where
the kernel lock ends up being taken twice. It is only ever
statement from the
Java garbage collector run (collecting the peer Java RexxEngines) right before the ooRexx instance
gets terminated from the Java side, as if this little time span makes the difference (at least on my
machine) and allows the Java callback into ooRexx to not block.
---rony
01dc8753d621()
01dc9e81b6b8()
00185b7fe1c8()
01dc9f0f5fb0()
01dcf3eee3a0()
---rony
On 13.08.2025 15:35, Rony G. Flatscher wrote:
Going after an occasional hang looking like this:
win32u.dll!NtUserMsgWaitForMultipleObjectsEx ()
user32.dl
!
Best regards
---rony
best regards,
René.
On 13 Aug 2025, at 20:01, Rony G. Flatscher wrote:
Yes, impressive, indeed, thank you, René.
However there is one important piece of information that is missing: that application did work a
couple of years ago, and sometimes works, mostly on Linu
lucky punch" hint. If there are no ideas,
then I need to systematically go through the code which may take a lot of time and effort.
---rony
On 13.08.2025 16:08, Gilbert Barmwater via Oorexx-devel wrote:
WOW! Unbelievable that AI could do that, at least to me. If most of that is, in fact,
deas, hints, and help are highly appreciated!
---rony
P.S.: Here the list of all threads, the one having Rexx code active (see above) is open (showing the
call stack):
Flagged 92240 Main Thread Main Thread
jvm.dll!7117e5ccNormal
Not Fla
The builds and tests with the commit incorporated run as before, there are no crashes that have been
observed. Hence I will update the related tracker items.
---rony
On 11.08.2025 14:25, Rony G. Flatscher wrote:
This patch makes the crashes go away with the test program:
Index
Hi P.O.,
On 11.08.2025 17:39, oorexx wrote:
The errors below in the tests should need a look at, I guess by Rony. The BSDs have some known
non-related problems and Windows 11 have lost the compiler (will fix that when back in Berlin),
but with the exception of these two errors all looks fine
ts of the interprter,
including a conceptual overview about flattening, rxapi and the like). This would benefit anyone in
this community who has a desire to understand the interpreter in an easy, quick manner!
---rony
On 06.08.2025 16:56, Rony G. Flatscher wrote:
Continuing to experiment with
ce.
You could cache the interpreter instance and use it later in your C++ program. You would use the
interpreter instance to carry out an AttachThread(), interact with ooRexx, and if done do a
DetachThread().
HTH
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
gets terminated
on a separate thread).
Since placing the Sleep(23) right in front of allActivities->append(activity) in
createCurrentActivity(), the test program seems to succeed when run in a separate, new session
repeatedly.
Any ideas, suggestions?
---rony
P.S.: Enclosed the test
) is via "Activity
*ActivityManager::attachThread()". Note, the test program does not cause attachThread() to be
invoked as it immediately uses the created interpreter instance to create and run a routine and then
terminates it on a separate thread.]
Not sure how to proceed. Any ideas, su
e interpreter with the id 5 does not create the output
"<{tid=1}>", so the question would be whether it gets run at all.
---rony
On 30.07.2025 16:50, Rony G. Flatscher wrote:
Using this e-mail thread to report new insights.
Prolog: first of all, it is a little bit bewitched
there the crash occurs (in the memoryObject.collectAndUninit() call branch).
(case 3) on the other hand does not shut down the interpreter, except after the last created
interpreter I8 got terminated on T6, causing I9 on T6 to shut down, which works without a crash in
this case.
Maybe these
On 29.07.2025 13:13, Rick McGuire wrote:
Nope, not even really possible. Once Terminate() is called, the instance
doesn't even exist any more.
Thanks.
---rony
On Tue, Jul 29, 2025 at 7:04 AM Rony G. Flatscher
wrote:
If an instance created with RexxCreateInterpreter(&insta
If an instance created with RexxCreateInterpreter(&instance, &rtc, options) gets terminated with
instance->Terminate(), is it necessary (or even possible) to invoke a rtc->DetachThread() thereafter?
---rony
___
Oorexx-devel maili
Reverted [r12999] and [r13000], hence trunk is now back at [r12998], updated the related RFE and bug
report.
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
very, very, bad thing to do and
it gains you nothing.
And of course, I would not want to do that at all!
---rony
On Mon, Jul 28, 2025 at 10:11 AM Rony G. Flatscher
wrote:
On 28.07.2025 15:02, Rony G. Flatscher wrote:
On 28.07.2025 13:51, Rick McGuire wrote:
You broke, you
On 28.07.2025 15:02, Rony G. Flatscher wrote:
On 28.07.2025 13:51, Rick McGuire wrote:
You broke, you fix it.
:)
But having said that, I see one obvious problem. Updating the instance field of an InstanceBlock
is a very, very, very bad idea. That was a new interpreter instance that was
sh anymore, hence planning to commit this version to
see how it fares on the Jenkins farm.
Any comments, hints, suggestions before doing so?
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/list
Committed with [r12999]: <http://sourceforge.net/p/oorexx/code-0/12999>.
---rony
On 27.07.2025 15:18, Rony G. Flatscher wrote:
On 27.07.2025 15:04, Rick McGuire wrote:
Actually, your version has a serious flaw in it. The line
+InstanceDetacher instDet = InstanceDe
stions?
---rony
On Sun, Jul 27, 2025 at 8:59 AM Rick McGuire wrote:
I would have put the attachThread() inside the constructor, but that works.
Rick
On Sun, Jul 27, 2025 at 8:49 AM Rony G. Flatscher
wrote:
On 27.07.2025 13:24, Rick McGuire wrote:
If an exc
stance;// interpreter instance
+};
+
+
#endif
Any comments, suggestions?
---rony
On Sun, Jul 27, 2025 at 6:51 AM Rony G. Flatscher
wrote:
It seems that the following patch fixes the reported crash:
Index: interpreter/runtime/Interpret
nce->InterpreterInstance::detachThread();
}
catch (ActivityException)
{
Any comments, suggestions?
---rony
On 23.12.2023 18:03, Rony G. Flatscher wrote:
Since last August a crash got reported in <https://sourceforge.net/p/oorexx/bugs/1872/> which can
be easily r
p archives would contain
the html related files in proper subdirectories named after the books they represent.
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Indeed, kudos to you, P.O.!
—-rony
Rony G. Flatscher (mobil/e)
> Am 06.06.2025 um 17:27 schrieb Michael Lueck :
>
> Greetings P.O.,
>
>
>
> ooRexx wrote:
>> As you might have noticed I have added the tools for release work on
>> Jenkins. I have given exa
Added RFE # 856 <https://sourceforge.net/p/oorexx/feature-requests/856/>.
---rony
On 22.05.2025 08:36, Till Winkler via Oorexx-devel wrote:
The option to use negative indexes is a really good idea that further increases the flexibility of
ooRexx. You probably already have this in min
from the
then current trunk.)
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
On 18.05.2025 20:00, Josep Maria Blasco wrote:
Missatge de Rony G. Flatscher del dia dv., 16 de maig
2025 a les 11:49:
(cut)
2) Adding new functionality to ooRexx, but being wary to "keep the language
small and easy to
learn".
(cut)
Maybe it would also be interesting
On 16.05.2025 14:01, Rony G. Flatscher wrote:
While building the release of 5.1.0 it turned out that P.O. had to install CMake 4.0 on Jenkins.
As ooRexx should be buildable on as many platforms as possible the question is, what the minimum
CMake version should be for ooRexx.
... cut
Hi Terry,
On 16.05.2025 20:34, taf wrote:
Well I was trying to kill several birds with one stone... I was running the latest oo-net-rexx
package from Rony. I'll follow your lead and download the debian 11 pkg. Thank you~
One remark ad the net-oo-rexx package: it actually consists o
s resolved, would it be sensible to increase the minimum supported version of
CMake to 3.5 or 3.6 or even to 3.10.2 without locking out platforms on which ooRexx is known to be
built?
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge
/jlfaucher/executor/blob/master/sandbox/jlf/_changes.md>. Please make yourself
acquainted such that we can start discussions on the developer lists about these experiments to
decide what to add how to the ooRexx mainline.
---
Any other suggestions and ideas welcome!
Any comments?
---rony
ot. If not, then the user can download the portable ooRexx for his
distribution and unzip it into the net-oo-rexx directory to replace the Ubuntu binaries.
So (like I also followed up on your last suggestion), are you sure that ooRexx compiled on Ubuntu
2404 will run on all Linux distros?
---rony
Hi there,
with r12982 the release of ooRexx 5.1.0 is done.
Please double-check whether something got overlooked or whether something is missing or wrong. If
necessary please adjust main/trunk/release-steps.md accordingly.
Now on to the symposium which starts in 75 minutes!
---rony
This is to announce the immediate availability of the release of ooRexx 5.1.0
ooRexx 5.1.0 passes the comprehensive unit tests and includes many bug fixes and enhancements. It
adds a new class, TraceObject, which allows for analyzing traces in unprecedented detail, making it
possible to debug m
e enough to
Vienna) or via Zoom.
* The symposium's registration page:
<https://www.rexxla.org/document.rsp?base=events&year=2025&doc=registration&title=Symposium%20Registration%20and%20Tickets>
* The symposium's schedule:
<https://
would be great.
Well I would even ask the entire world to lend a helping hand whenever
possible! :)
Those who arrived already in Vienna do sightseeing and sometimes join already for dinner. Looking
forward for the start of the symposium with the tutorials tomorrow.
Best re
self-heal once I have bumped the ORX_MINOR version?
Probably.
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
(https://www.rexxla.org/events/schedule.rsp?year=2025).
You can still register for the symposium attending either in person or via Zoom at
<https://www.rexxla.org/document.rsp?base=events&year=2025&doc=registration&title=Symposium%20Registration%20and%
+1
Thank you very much for all of your efforts, P.O.!
The artifcats are currently at
<https://sourceforge.net/projects/oorexx/files/oorexx/5.1.0ReleaseCandidate/> and
<https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.1.0ReleaseCandidate/>.
---rony
On 03.05.2025 0
cmake_minimum_required (VERSION 3.12)
else()
#for other platforms
cmake_minimum_required (VERSION*3.5*)
endif()
cmake_policy(VERSION 2.8...*3.5*)
Not sure what the increase to 3.5 in cmake_policy causes. Can anyone can shed some light on it? Do
we still need it?
---rony
P.S
f the
native libraries used for
the testunit. Hence one would have to adjust the library locations to the
version created by
"branches/5.1.0".
Will create a standalone version of "main/branches/5.1.0" and run the "test/branches/5.1.0" test
suite against it.
-
'/docs/branches/5.1.0'
However, SourceForge reported by e-mail that the comit was successful with
revision 12972.
Just to let you know in case there are problems creating the documentation for
5.1.0
---rony
___
Oorexx-dev
to 3.12 which is newer then 3.5 (cf. <https://cmake.org/files/>
which makes clear that 3.5 is older than 3.12 which therefore should be used as the minimum version).
The rpath problem was originally pointed out by Enrico Sorichetti, if not
mistaken.
HTH
---rony
P.S.: Too many project
(APPLE)
*# apple builds with cmake version smaller than 3.12 have an @rpath problem*
cmake_minimum_required (VERSION*3.12*)
else ()
# for other platforms
cmake_minimum_required (VERSION 2.8.12)
endif ()
---rony
On 01.05.2025 23:12, ooRexx wrote:
Hi René,
Erich
ed by Dom Wise on 2025-03-12 -> 2025-03-18
)
5: # 1994 Duplicate trace line if using "forward" without "continue"
(entered by Rony G. Flatscher on 2025-01-22 ->
2025-03-15 )
6: # 1989 SysTextScreenRead fai
On 28.04.2025 14:46, P.O. Jonsson wrote:
Am 28.04.2025 um 13:31 schrieb Rony G. Flatscher :
Dear P.O.,
On 27.04.2025 22:54, P.O. Jonsson wrote:
Tomorrow I will review those part related to the release process that I need to do, With the
script I have developed much of the release process will
set to May, 4th, 2024 (the first
day of the symposium). The building itself should be done by Thursday midnight such that the test
suite can run against it.
Cheers
---rony
Am 27.04.2025 um 22:02 schrieb Rony G. Flatscher :
The documented release instructions for 5.0.0 can be found in &
o 5.1.0 and the like) and post any remarks, feedback.
---rony
P.S.: Also, after the 5.1.0 release (and after the symposium) it would be nice to assess whether it
is possible to fully automate the creation of a release for future releases.
___
Oo
list each command on a separate line in your preferred case. Cf. the
readme information about creating customized auto-complete names and where to place those files.
---rony
On 27.04.2025 13:19, Rony Flatscher via groups.io wrote:
As you may know, Alexander Seik has been taking on the task to
ack that you might have (also positive feedback, if you have any! :) ). Alexander
is a member and following the RexxLA e-mails.
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
er bugs, IMHO there is no reason not to release the current version, making the
International Rexx symposium the event to communicate and report on it! Not releasing it hinders the
ooRexx community to take advantage of the new features coming with ooRexx, e.g. the new TraceObject
class enhancing
On 25.04.2025 09:29, ooRexx wrote:
Hi Rony, I think that is a good idea, I do not know of any bugs/features that are that serious
that they are /show stoppers?/ Anyone?
I can help with managing the build system next week. I will finalise my work
before then.
I propose that we set up the
Suggesting to prepare a general availability version for ooRexx 5.1.0 with the aim to release it
next week such that we have a new release for this year's International Rexx symposium in Vienna.
Any thaughts, comments?
---rony
___
Oorexx-
x distributions, then it
may make sense to label it generically as "Linux". OTOH, if the Ubuntu2404 does not work on all
64-bit Linux versions, then it would be dangerous to label it "Linux" as it would be misleading then.
What do you think?
---rony
On 2025-04-
Forwarded Message
Subject:[rexxla-members] Announcement: new "packages*.zip" and new
"net-oo-rexx*.zip"
Resent-Date:Thu, 03 Apr 2025 13:01:54 -0700
Resent-From:rony.flatsc...@wu.ac.at
Date: Thu, 3 Apr 2025 22:01:29 +0200
From: Rony Fla
Created an RFE: <https://sourceforge.net/p/oorexx/feature-requests/853/>
---rony
On 20.03.2025 12:34, Rony G. Flatscher wrote:
Hi Josep Maria,
On 19.03.2025 17:30, Josep Maria Blasco wrote:
Some comments more
(cut)
To indicate which condition should be propagated in this
Hi Josep Maria,
On 19.03.2025 17:30, Josep Maria Blasco wrote:
Some comments more
(cut)
To indicate which condition should be propagated in this manner, one
could perhaps allow
for the subkeyword PROPAGATE in addition to SYNTAX and CONDITION, e.g.,
"::OPTIONS
conditio
SYNTAX and CONDITION, e.g., "::OPTIONS
condition
SYNTAX|CONDITION|PROPAGATE", where 'condition' would be any of the condition
names that can be
supplied to the RAISE keyword instruction plus 'ALL' to mean all conditions.
So the questions at this point would be:
* Wou
n
the 'options' directive, and there would be no need to memorize exceptions (increasing the cognitive
load). In the syntax condition case, the subkeyword CONDITION would have no effect as a syntax
condition would be propagated as a syntax condition (as would the subkeyword SYNTAX).
Any comments from others reading this group?
---rony
On 13.03.2025 12:49, Rony G. Flatscher wrote:
Maybe a few remarks:
* currently the code works for orderedCollections; it also will convert any
orderedCollection,
not only stems according to the type supplied to the from class
Hi Leslie,
On 13.03.2025 06:01, J Leslie Turriff via Oorexx-devel wrote:
On 2025-03-12 07:56:52 Rony G. Flatscher wrote:
On 12.03.2025 12:44, Michael Lueck wrote:
Greetings Rony,
Rony G. Flatscher wrote:
As such I would assume to be safe to add the hashbang "#!/usr/bin/env
rexx&qu
Collections, one
would have to define individual "to..." instance methods (like "toQueue",
"toCircularQueue",
"toList", "toArray", "toStem"); it seems that using a class method "from"
will keep the
interface sma
Hi Michael,
On 13.03.2025 12:39, Michael Lueck wrote:
Rony G. Flatscher wrote:
On 13.03.2025 02:53, Michael Lueck wrote:
Michael Lueck wrote:
I am working through revering my LDSTextFile class to use Stem storage rather than Array
storage. My plan is to be able to exchange version of
is as part of my Symposium presentation.
The code is pretty well commented but I should point out that when a stem instance is to be
converted, there exists the possibility that it is sparse, i.e. an expected tail is missing. E.g.
cv.0 = 3; cv.1 = 'Gil'; cv.3 = 'Rony
/usr/local/share/ooRexx/samples/api/classic/callrexx/startrx3.rex
/usr/local/share/ooRexx/samples/api/classic/rexxapi1/apitest1.rex
/usr/local/share/ooRexx/samples/api/classic/rexxapi2/apitest2.rex
/usr/local/share/ooRexx/samples/api/classic/rexxapi3/apitest3.rex
Thanks for this updated list.
Cheer
tent of an array to write to a file.
HTH
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
On 12.03.2025 12:44, Michael Lueck wrote:
Greetings Rony,
Rony G. Flatscher wrote:
As such I would assume to be safe to add the hashbang "#!/usr/bin/env rexx" as the first line
directly to all those files that you found not to have it. Then all Rexx scripts would adhere to the
n will not really change on Unix systems (changing this convention on Unix
would affect literally billions of files).
As such I would assume to be safe to add the hashbang "#!/usr/bin/env rexx" as the first line
directly to all those files that you found not to have it. Then all Rex
locate-external-keys s...@debian.org
Thought that to be interesting for the ooRexx project as well, now that projects start to explicitly
support this.
---rony
P.S.: Here the homepage for DBus: <https://www.freedesktop.org/wiki/Software/dbus/> which is not
only available on most Linux
ble versions of ooRexx on the same machine at the same time.
---rony
On 2025-03-11 15:21:25 Rony G. Flatscher wrote:
Hi Michael,
On 10.03.2025 20:44, Michael Lueck wrote:
Rony G. Flatscher wrote:
Hi Michael,
could you please run your programs against 5.0.0 or 5.1.0 and report
about your
Hi Gil,
here the ticket: <https://sourceforge.net/p/oorexx/feature-requests/850/>
In the meantime I added a target of "5.2.0" to the bug and the rfe trackers.
---rony
On 10.03.2025 18:00, Rony G. Flatscher wrote:
Hi Gil,
On 09.03.2025 14:45, Gilbert Barmwater wrote:
M
Hi Michael,
On 10.03.2025 20:44, Michael Lueck wrote:
Rony G. Flatscher wrote:
Hi Michael,
could you please run your programs against 5.0.0 or 5.1.0 and report about your
findings?
(It may be the case that the slowness you report has gone.)
Certainly!
I currently have this build on my
always use fully
qualified file names. (A classic "pre-justice" assuming that the error had to do in this case with
employing commands which caused "complex possible causes" to be thought of that were misleading. :( )
Will fix and test and then commit.
---rony
On 10.0
unity decides to open an RFE.
Will do to get to see your implementation, thanks for the offer! :)
Cheers
---rony
On 3/9/2025 6:39 AM, Rony G. Flatscher wrote:
1) ad stem arrays
==
Stem arrays have been conceived and used since the inception of Rexx.
The pattern is simple:
Hi P.O.,
fixed with [r12935].
Cheers
---rony
On 10.03.2025 18:00, Rony G. Flatscher wrote:
Hi P.O.,
please forget my previous post, there was a stupid error in the test that caused the error: while
testing the single test unit the current directory was the same in which the testfiles got
On 10.03.2025 18:30, ooRexx wrote:
This was a documentation bug report I filed for 5.0.0 that has not been dealt with then or since.
It does not have an owner and no work has been done on it. what do we do with this (and similar
cases), do we just bump up the milestone?
This may have been fixe
Hi Josep Maria,
On 09.03.2025 14:40, Josep Maria Blasco wrote:
Missatge de Rony G. Flatscher del dia dg., 9 de març
2025 a les 14:04:
(cut)
1a) In order to create an ooRexx array from a stem array the following
method should be
added to the stem class
Hi Michael,
could you please run your programs against 5.0.0 or 5.1.0 and report about your
findings?
(It may be the case that the slowness you report has gone.)
Cheers
---rony
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
1 - 100 of 2155 matches
Mail list logo
