Activity for ooRexx (Open Object Rexx)
-
Rony G. Flatscher committed [r13164] on Code SVN
20260426 Releasing ooRexx 5.2.0, moving branches/5.2.0 to releases/5.2.0
-
ooRexx (Open Object Rexx) released /oorexx/5.2.0/portable/oorexx-5.2.0-13156.fedora43.x86_64-portable-release.zip
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Graham Norris modified a comment on ticket #2059
This discusion is getting a bit disjointed, but I did that: https://sourceforge.net/p/oorexx/bugs/2059/#1762 Update: I have just rebuilt OORexx 4.2, as I have done many times before, but this time just to check that it will still build with the more recent NSIS version. It does. The VC version is the same, NSIS version is the same, but OORexx 5.2's build process (from its CMake-build-readme.txt) still fails: "NMAKE : fatal error U1073: don't know how to make 'nsis_template_installer'". (After clearing...
-
Алексей Евгеньевич Тарасов modified a comment on discussion Help
Perhaps I'm using the "procedure" reference incorrectly. This is simply based on my previous experience. I'll give a simplified example of a possible problem. We have a database access class. The queries can be different: select/insert/... The queries can be executed in parallel. Each query is handled by its own method. When initializing the database connection, common parameters are set that are used by all methods. Each query receives an input string with parameters. To parse the input string,...
-
Perhaps I'm using the "procedure" reference incorrectly. This is simply based on my previous experience. I'll give a simplified example of a possible problem. We have a database access class. The queries can be different: select/insert/... The queries can be executed in parallel. Each query is handled by its own method. When initializing the database connection, common parameters are set that are used by all methods. Each query receives an input string with parameters. To parse the input string,...
-
Perhaps I'm using the "procedure" reference incorrectly. This is simply based on my previous experience. I'll give a simplified example of a possible problem. We have a database access class. The queries can be different: select/insert/... The queries can be executed in parallel. Each query is handled by its own method. When initializing the database connection, common parameters are set that are used by all methods. Each query receives an input string with parameters. To parse the input string,...
-
Perhaps I'm using the "procedure" reference incorrectly. This is simply based on my previous experience. I'll give a simplified example of a possible problem. We have a database access class. The queries can be different: select/insert/... The queries can be executed in parallel. Each query is handled by its own method. When initializing the database connection, common parameters are set that are used by all methods. Each query receives an input string with parameters. To parse the input string,...
-
jfaucher posted a comment on discussion Help
ooRexx5 supports "variable reference term" (search that in rexxref). That's a way to "create variables that are accessible after its call ends." But your other requirement 'the "procedure" to access the namespace of the method it was called from.' is not covered by variable reference. That makes me think to a closure. See if this implementation is what you need, it works with ooRexx5: https://github.com/jlfaucher/executor/blob/9ae8391b6f1fa358b90c059782bdcf95d6a449f8/sandbox/jlf/packages/extension/callable_std.cls#L129-L158...
-
Let me rephrase the question slightly. I need methods to create their own namespaces, and the "procedure" to access the namespace of the method it was called from. And, just as importantly, the "procedure" should be able to create variables that are accessible after its call ends. This problem seems unsolvable right now. I'll have to call the "procedure" as a method and return a stem, which I can use to create local variables in the loop. It must be said that in classic Rexx this problem is solved...
-
Let me rephrase the question slightly. I need methods to create their own namespaces, and the "procedure" to access the namespace of the method it was called from. And, just as importantly, the "procedure" should be able to create variables that are accessible after its call ends. This problem seems unsolvable right now. I'll have to call the "procedure" as a method and return a stem, which I can use to create local variables in the loop.
-
This discusion is getting a bit disjointed, but I did that: https://sourceforge.net/p/oorexx/bugs/2059/#1762
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Per Olov Jonsson committed [r13163] on Code SVN
Updating copyright for macOS installer
-
Please be aware that we use a special version of nsis with long strings support, if you have downloaded the latest version this might be the reason for your failure. Please use the zipped version from above. There is no need to install it, just unsip it somewhere and add that directory to the path. You should uninstall the newer version first.
-
Here's the situation. I have a class with several methods that need to run in parallel. They all have access to class variables. Each method also has internal variables whose names are the same in all methods. We need to have common code for all methods that will access both class variables and method variables. Here's a rough outline. class b=5 method1 unguarded expose b a=1 call procedure method2 unguarded expose b a=2 call procedure method3 unguarded expose b a=3 call procedure procedure expose...
-
The nsis installer build requires that the DOC_SOURCE_DIR be set to the location of the doc artifacts that are included in the installer. Have you done that? Here is what happens when I run these steps (in a batch file because I am repeating them rather often!) D:\Development\OORexx\OORexx5.2build>..\buildit5.2.cmd Xtras location: D:\Development\OORexx\oorexxextras Source location: D:\Development\OORexx\oorexx5.2SVN Document location: D:\Downloads\ooRexx\5\ooRexx-5.2.0-all(docs) Build location: D:\Development\OORexx\OORexx5.2build\...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
