Re: [Oorexx-devel] Another question

nceMethods() method to retrieve them. Rick On Mon, Jun 3, 2024 at 3:17 PM Gilbert Barmwater wrote: Let's say there is a class defined via ::class myClass.  It has numerous methods, both instance methods and class methods. If I want to enumerate the instance methods, supp

[Oorexx-devel] Another question

Let's say there is a class defined via ::class myClass.  It has numerous methods, both instance methods and class methods. If I want to enumerate the instance methods, supp = .myClass~methods will give me a supplier that will do so.  If I specify supp = .myClass~methods(.nil), the supplied

Re: [Oorexx-devel] Clarification on .package~new

on the basic structure of the program not changing but I don't have any "extra" files being created. Hopefully this explanation will help someone in the future faced with a similar situation. Gil On 6/1/2024 10:38 AM, Rony G. Flatscher wrote: On 31.05.2024 20:29, Gilbert Barmwater w

[Oorexx-devel] Clarification on .package~new

I've been experimenting with the .package class and have run into somewhat puzzling behavior.  I am trying to create a .package object from a file which, according to the documentation, should look like this: thePkg=.package~new(fileName) When I do this I DO get a package in thePkg, BUT the

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

Hi P.O., I noticed from the recent SVN activity that all of the 5.1.0 documents had been rebuilt.  Was this intentional or an artifact of your testing?  Just curious . Gil On 4/20/2024 8:42 AM, ooRexx wrote: On 20. Apr 2024, at 13:34, Rony G. Flatscher wrote: Hi P.O., thank you for

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

Actually, I believe that the documentation is inaccurate.  If one specifies TRACE L, ooRexx "Traces method and routine invocations, internal subroutine calls, transfers of control because of the SIGNAL instruction, and labels passed during program execution.". So the >I> entry also appears for

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

Feel free to ignore this as I am NOT a MacOS user.  I feel that having 2 packages is the more straightforward way to proceed rather than continuing with the complexity of a universal package even though that may be "common" on the MacOS platform.  My 2 cents, FWIW. Gil On 1/13/2024 2:12 PM,

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

to do a bug-fix release - 5.0.1 - or a new feature release - 5.1.0 - it is time to clean up this "unfinished business". On 11/29/2023 7:11 AM, Rony G. Flatscher wrote: On 24.11.2023 01:05, Gilbert Barmwater wrote: If the consensus is to do this, can we make a concerted effor

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

If the consensus is to do this, can we make a concerted effort to get the bugs and RFEs that were in 5.0.0 but were not marked as "pending" - usually as "accepted" - finally to a finished state, namely "pending"?  There has been a good amount of work on this but I'd really want to see ALL of

Re: [Oorexx-devel] Jenkins

OK, great!  Thanks Rony! On 10/28/2023 9:23 AM, Rony G. Flatscher wrote: 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 i

Re: [Oorexx-devel] Jenkins

Hi P.O., 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 of the documentation build tools.  Rony

Re: [Oorexx-devel] Committing change

I support this as well +1 On 9/22/2023 4:26 PM, 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

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

I suspect that the problem resides with the build process for the Windows installer - NSIS.  It incorporates the PDF documentation into the .exe file and should be using the files from .../oorexx-docs/5.1.0beta/.  Although that directory now contains new versions of the PDFs, the r12722

Re: [Oorexx-devel] Latest Builds

And all is good.  Was able to download and install 12694 successfully. Gil On 6/16/2023 11:34 AM, Gilbert Barmwater wrote: I think it is resolved by updating Windows Defender.  Once 12694 builds I'll try it again.  Thanks, GB On 6/16/2023 11:29 AM, P.O. Jonsson wrote: Hi Gil, Just

Re: [Oorexx-devel] Latest Builds

not yet on Sourceforge. Please provide the revision and any additional information like what antivirus software you are using and I will have a check also Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se Am 16.06.2023 um 15:49 schrieb Gilbert Barmwater : Has anyone had any success

Re: [Oorexx-devel] Latest Builds

=> 12693  on Windows 11.  Usually the first time I click "run anyway" it silently terminates the process without running.  This time it installed first time. Jon On Fri, 16 Jun 2023 at 15:20, Gilbert Barmwater wrote: Has anyone had any success in downloadi

[Oorexx-devel] Latest Builds

Has anyone had any success in downloading the latest Windows 64-bit build?  I tried to update twice this morning and got messages that the file couldn't be downloaded because it had a virus.  Now I normally have to jump through hoops anyway because Windows tells me that the file isn't normally

Re: [Oorexx-devel] [oorexx:bugs] #1897 Entry missing in Windows installer

On 5/10/2023 1:27 PM, Rick McGuire wrote: On Wed, May 10, 2023 at 12:22 PM ooRexx wrote: I am sorry but I have to come back to this item: What is the difference between the milestones 5.0.0, 5.0.1 and 5.1.0? That indicates which release the

Re: [Oorexx-devel] Conventions

I think this needs more discussion before making, what seems on the surface to be, a "trivial" change. When RexxLA received the source for Object Rexx from IBM, there was quite a bit of discussion on what the project should be called with the eventual decision being "ooRexx".  I'm sure the

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

So it turns out that under Windows, it is easy to obtain the thread ID of the current running code.  My framework now does that so it might be of use, as is, to anyone needing to know which thread executed the line being traced.  Gil On 4/1/2023 5:01 PM, Gilbert Barmwater wrote: Well, FWIW, I

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

Well, FWIW, I thought so too.  Just for fun I have implemented a working framework of what I described later in this thread.  Of course, even though it can modify the trace output, it does not actually put the "real" values in as that would require either the modifications to the .stackframe

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

On 3/25/2023 11:58 AM, 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 of outputStream, that implemented a SAY method which would "collect" the additi

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

Let me see if I've got this.  If there was a class, perhaps a subclass of outputStream, that implemented a SAY method which would "collect" the additional multi-threading information and add it to the argument that it receives, then one would only need to create an instance of that class

Re: [Oorexx-devel] Musings with tracing multithreaded ooRexx programs, mt91.rex: on two Rexx interpreter instances (RII)

Not being a user who writes multi-threaded ooRexx programs, I have remained silent until now.  However, it seems to me that there are enough objections to the proposal that would add this to TRACE that we should consider alternatives. I appreciate the need for the information and the work done

Re: [Oorexx-devel] Request for fast help on finally resolving 5.0.0 related open partial tracker items ...

On 2/6/2023 6:50 AM, Rony G. Flatscher wrote: Hi Jon, On 05.02.2023 22:34, Sahananda Sahananda wrote: I have updated and committed the xml file.  I think that now an automatic rebuild of the documentation will be triggered.  Is that right? Not sure. An automatic build gets triggered if code

Re: [Oorexx-devel] Problem with bldoc_orx/docprep.rex

Thanks for the report Rony.  I will investigate the problem and report back as time permits. Gil On 2/5/2023 7:53 AM, Rony G. Flatscher wrote: This is mostly addressed to Gil. Using your latest drop of bldoc_orx (currently on Windows), trying to create the rexxextensions book. Before

Re: [Oorexx-devel] Ad svn revision number ...

+1 Gil B. On 1/25/2023 9:42 AM, Rony G. Flatscher wrote: The examples were taken after having done an "svn update" in "main/trunk", but not in "docs/trunk" and "test/trunk". After doing a "svn update" over the entire project the "Revision" field carries the same number for all three

Re: [Oorexx-devel] Ad Commons_Content directory (Re: More info on Jenkins

problem with using my docbuild tools on Ubuntu, they used to work but when I retry them now they do not work. Could be the same problem. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se Am 03.01.2023 um 23:04 schrieb Gilbert Barmwater : Thanks for catching this Rony!  I will inv

Re: [Oorexx-devel] Ad Commons_Content directory (Re: More info on Jenkins

Thanks for catching this Rony!  I will investigate as I have time along with the problem with setup.rex on Windows using a non-existent FOP mirror. Gil On 1/3/2023 12:32 PM, Rony G. Flatscher wrote: On 03.01.2023 15:00, Gilbert Barmwater wrote: While being there we should also consider

Re: [Oorexx-devel] More info on Jenkins

See below; trimmed some of the post... On 1/3/2023 11:36 AM, Gilbert Barmwater wrote: I hope to reply specifically later today.  GB On 1/3/2023 10:02 AM, P.O. Jonsson wrote: Dear Gil and Rony, I have responded to your comments below. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se

Re: [Oorexx-devel] More info on Jenkins

I hope to reply specifically later today.  GB On 1/3/2023 10:02 AM, P.O. Jonsson wrote: Dear Gil and Rony, I have responded to your comments below. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se Am 03.01.2023 um 15:00 schrieb Gilbert Barmwater : I was going to reply to the OP

Re: [Oorexx-devel] More info on Jenkins

I was going to reply to the OP that I saw last night but then I saw this reply from Rony so I have added my comments below. On 1/3/2023 5:44 AM, Rony G. Flatscher wrote: Thank you (and also Gil) for all of your efforts! On 03.01.2023 00:18, ooRexx wrote: My attempt to always have the

Re: [Oorexx-devel] At the end of the 5.0.0 release cycle and beyond ...

See below... On 1/1/2023 6:38 PM, ooRexx wrote: On 1. Jan 2023, at 17:43, Rony G. Flatscher wrote: Brief info on today's work: * updating the tickets from "pending" and "accepted" with no open items to "closed": did not write a utility after finding out about "bulk-edit", all four

Re: [Oorexx-devel] Release 5.0.0

Just a thought but didn't we start with our code in CVS rather than SVN? Perhaps that is why 3.0.0 and 3.0.1 are missing. Gil On 12/31/2022 12:14 PM, Rony G. Flatscher wrote: On 30.12.2022 13:21, ooRexx wrote: - Sourceforge could bring most of the documentation back, 3.0.0 and 3.0.1 I

Re: [Oorexx-devel] Release of ooRexx 5

, much of it unseen by the development community! I note everything for the next time we intend to do a release For information Jenkins is now on the latest LTS release version, 2.375.1 Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se On 28. Dec 2022, at 15:40, Gilbert Barmwater

Re: [Oorexx-devel] Release of ooRexx 5

o no actual data was present, just the layout so to speak. I hope there is a backup on Sourceforge, I have not yet heard from the support there. I am upgrading the Jenkins system today and will start it later tonight. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se On 26. Dec 2022, a

Re: [Oorexx-devel] Ad changing ticket states

Well, I figured the ones I opened should be closed by me so I did.  I also did RFE 4 since I was heavily involved in making that happen.  I did them manually but as there are so many others remaining perhaps we should look at automating the process. Re the items with TODO's:  I have edited

Re: [Oorexx-devel] Release of ooRexx 5

I have 4.2.0 for Windows 64 bit installed which has the included PDFs.  Let me know if you need them. Gil On 12/25/2022 6:03 PM, ooRexx wrote: I have some god news and some bad news The good news: FreeBSD is now revision 12583, I rebuilt it manually macOS is also 12583, but now with the

Re: [Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

Saw that new Windows builds were available so I downloaded the 64-bit version and installed it.  Works great and the docs are correct!  Well done everyone! Gil On 12/23/2022 11:45 AM, Gilbert Barmwater wrote: Rony, P.O. indicated that he can trigger a build manually on Jenkins so it should

Re: [Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

Rony, P.O. indicated that he can trigger a build manually on Jenkins so it should NOT be necessary to do any further SVN updates.  FWIW, Gil On 12/23/2022 11:33 AM, Rony G. Flatscher wrote: On 23.12.2022 17:29, ooRexx wrote: Due to this unnecessary commit Windows and macOS are now getting

Re: [Oorexx-devel] Current state, lists to write to (Re: Proposed text ...

Fix typo: "...you may consider to joining..." -> "... you may consider joining..." On 12/23/2022 8:52 AM, Rony G. Flatscher wrote: First of all, thank you all for your feedback on the text! On 23.12.2022 14:41, Sahananda Sahananda wrote: Just a reminder, we have the ooRexx Announcements list

Re: [Oorexx-devel] Proposed text ...

Just a few minor language changes :-) general -> generally (first sentence) to join -> joining (paragraph near the bottom) Gil On 12/23/2022 7:46 AM, Rony G. Flatscher wrote: Here the proposed (it should not be too long, it should carry the most important information and make the readers

Re: [Oorexx-devel] docs/branches/5.0.0: updated copyright, added & committed "${book}/revision_info.txt", updated & commited EDITION entity; scripts checked in

Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se On 22. Dec 2022, at 23:18, Gilbert Barmwater wrote: So, as Jon has noted, on Windows the installer includes the documentation which will be the "current" set as of the time the Windows build is executed.  Now if one

Re: [Oorexx-devel] docs/branches/5.0.0: updated copyright, added & committed "${book}/revision_info.txt", updated & commited EDITION entity; scripts checked in

ote: On 22.12.2022 19:10, Gilbert Barmwater wrote: If this is the final step, I think we should have P.O. build a new set of documents and upload them to sourceforge, replacing those that are there if possible.  Then I would encourage everyone on this list to retrieve them and review them for

Re: [Oorexx-devel] docs/branches/5.0.0: updated copyright, added & committed "${book}/revision_info.txt", updated & commited EDITION entity; scripts checked in

If this is the final step, I think we should have P.O. build a new set of documents and upload them to sourceforge, replacing those that are there if possible.  Then I would encourage everyone on this list to retrieve them and review them for appearance at least.  Barring any really bad

Re: [Oorexx-devel] Another problem for the doc revision and a possible solution (Re: updateEntityValues with revision information

do it every time we build the document. On 12/22/2022 11:52 AM, Gilbert Barmwater wrote: Sorry I wasn't more clear in my final comments.  If one could determine the "real" dates, probably manually, and update and "commit" the values in the *.ent files, then the "automate

Re: [Oorexx-devel] Another problem for the doc revision and a possible solution (Re: updateEntityValues with revision information

revision_info.txt files, all it would take is to go through them, update the *.ent files and commit the changes. Then the code in docprep.rex could be commented out.  Builds would then have the correct revision number and date. Gil On 12/22/2022 11:32 AM, Rony G. Flatscher wrote: On 22.12

Re: [Oorexx-devel] Another problem for the doc revision and a possible solution (Re: updateEntityValues with revision information

See below... On 12/22/2022 9:35 AM, Rony G. Flatscher wrote: On 22.12.2022 14:58, Gilbert Barmwater wrote: Back in July (seems like years ago), I modified the ooRexx version of the document build tools.  As part of that effort, I did some work to have docprep.rex modify the VERSION

Re: [Oorexx-devel] Another problem for the doc revision and a possible solution (Re: updateEntityValues with revision information

Back in July (seems like years ago), I modified the ooRexx version of the document build tools.  As part of that effort, I did some work to have docprep.rex modify the VERSION and EDITION ENTITIES "on the fly" (Note only in the working copy).  Have a look in the tools/bldoc_orx folder at

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

as proposed by Rony. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se On 22. Dec 2022, at 14:07, Gilbert Barmwater wrote: As I suspected, this fixed the problem! Good work! One reason I wanted to look at the HTML version was to see if the authors are listed on the title page there too

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

.  The bottom line is we don't need any changes for the HTML versions. Gil On 12/21/2022 7:15 PM, Gilbert Barmwater wrote: I'll have a look first thing in the AM.  I'm sure that this will fix the problem. I think documenting the dependency in the HowTo should be sufficient. And thanks for all

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

such changes be added to the release-steps.txt? They are not per see related to the new release. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se On 21. Dec 2022, at 15:57, Gilbert Barmwater wrote: Hi P.O., I saw new uploads of the Release Candidate documents so I tried downloading

Re: [Oorexx-devel] pdf.xsl (Re: Going ahead with ... (Re: Documentation: remove author list from front page ?

Done for bldoc_rx.  Will also update the bldoc_win folder in both places as well. Gil On 12/21/2022 2:10 PM, Gilbert Barmwater wrote: OK, finally had a chance to look at the proposed 1 line change and to test it out and it looks good.  As this file has other modifications which

Re: [Oorexx-devel] pdf.xsl (Re: Going ahead with ... (Re: Documentation: remove author list from front page ?

OK, finally had a chance to look at the proposed 1 line change and to test it out and it looks good.  As this file has other modifications which are documented in sources.txt, I will update both files shortly and commit them to both trunk and branches. Gil On 12/20/2022 11:22 AM, Gilbert

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

? Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se On 21. Dec 2022, at 16:27, Gilbert Barmwater wrote: +1 Thanks for investigating! On 12/21/2022 10:21 AM, ooRexx wrote: On 21. Dec 2022, at 15:57, Gilbert Barmwater wrote: Hi P.O., I saw new uploads of the Release Candidate documents so I

Re: [Oorexx-devel] tools/bldoc_orx/setup.rex error, non existing server?

When I first wrote setup.rex the goal was to make it easy for the new (Windows) user to get all the pieces needed to build the ooRexx documentation.  Most of those pieces were pretty straight forward as they were fairly static so coding web addresses and file names was not a problem.  FOP

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

+1 Thanks for investigating! On 12/21/2022 10:21 AM, ooRexx wrote: On 21. Dec 2022, at 15:57, Gilbert Barmwater wrote: Hi P.O., I saw new uploads of the Release Candidate documents so I tried downloading the reexxref_html zip file to have a look. Although it downloads some 5.3Mb, when I

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

Hi P.O., I saw new uploads of the Release Candidate documents so I tried downloading the reexxref_html zip file to have a look. Although it downloads some 5.3Mb, when I attempt to look inside the downloaded file or extract all the pieces, I see an empty folder!  I'm on Windows 10 if that

Re: [Oorexx-devel] Ad state of docs/branches/5.0.0

Good morning!  I am planning on working on this today, I just need a little more time.  I will also look at the revision string question as well. Gil On 12/21/2022 6:21 AM, Rony G. Flatscher wrote: Dear P.O., On 21.12.2022 09:45, ooRexx wrote: When I looked a bit closer I found the change

Re: [Oorexx-devel] pdf.xsl (Re: Going ahead with ... (Re: Documentation: remove author list from front page ?

Probably won't have time to do this until tomorrow. Gil On 12/20/2022 10:44 AM, Rony G. Flatscher wrote: O.k. managed to cause the authors to not be included on the title page. For this to happen I had to change the pdf.xsl file which I attach for inspection: look for the needle "rgf

Re: [Oorexx-devel] docs Re: Ad current release 5.0.0

OK, that explains it. +1 On 12/19/2022 11:57 AM, Rick McGuire wrote: On Mon, Dec 19, 2022 at 11:54 AM Gilbert Barmwater wrote: OK, I can see that but in looking at the 4.2.0 Rexx Ref. document, I don't see them so I assumed they should go away.  Totally agree that they should

Re: [Oorexx-devel] docs Re: Ad current release 5.0.0

of anybody making the upgrade. However, removing them from the trunk version should be added to the release process checklist. Rick On Mon, Dec 19, 2022 at 10:13 AM Gilbert Barmwater wrote: I have downloaded and installed the 5.0.0 Release Candidate and noticed that the docs still

Re: [Oorexx-devel] docs Re: Ad current release 5.0.0

I have downloaded and installed the 5.0.0 Release Candidate and noticed that the docs still have the *CHG* and *NEW* flags in them.  I believe they are normally removed once a release is made but I am not sure what the process is to make that happen.  Can anyone comment on this?  BTW, the code

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

Just one more comment that I feel should not be overlooked.  As we review the "accepted" items we may find a small change - adding a test or updating the docs - would allow the status to be upgraded to "pending".  If that is the case and those changes are made, they MUST be made in TWO places

Re: [Oorexx-devel] Release ooRexx 5.0.0: Step 1 (Re: Proposal for creating a release version for ooRexx 5.0.0

OK thanks Rick.  At least I'm not totally delusional :-) Gil On 12/14/2022 3:11 PM, Rick McGuire wrote: On Wed, Dec 14, 2022 at 2:05 PM Gilbert Barmwater wrote: I seem to remember, perhaps incorrectly, that there was some documentation on the steps necessary in order to create

Re: [Oorexx-devel] Release ooRexx 5.0.0: Step 1 (Re: Proposal for creating a release version for ooRexx 5.0.0

I seem to remember, perhaps incorrectly, that there was some documentation on the steps necessary in order to create a new release of ooRexx.  However, my cursory attempt at locating it has come up empty.  If anyone else remembers such a document and, more importantly, where it is, please let

Re: [Oorexx-devel] 4.2/5.0 Coexistence on Windows

mmand line where you want to run oorexx, set the path to point to the appropriate version. 3) Run that version. The big issue with using multiple versions was always rxapi. With that problem being resolved in 5.0.0, the two versions can happily coexist. Rick On Mon, Dec 5, 2022 at 2:29 PM Gilbe

[Oorexx-devel] 4.2/5.0 Coexistence on Windows

A recent discussion on RFE 715 led to the question of whether or not ooRexx 4.2.0 and 5.0.0 could coexist on a system.  I am starting this thread to hopefully expose the discussion to a larger audience.  As my experience is restricted to Windows systems, I am restricting the subject to that

Re: [Oorexx-devel] ooRexx /dev/null for redirected command handler

that works on both you need to add a line: discard = (.rexxinfo~platform == 'LINUX')~?('/dev/null', 'nul:') address system 'some command' with error stream (discard) FWIW, YMMV. Gil On 12/3/2022 3:57 PM, Gilbert Barmwater wrote: I was going to suggest address system 'some command' with error usi

Re: [Oorexx-devel] ooRexx /dev/null for redirected command handler

I was going to suggest address system 'some command' with error using (.array~new) but I like your answer better :-) Gil On 12/3/2022 2:39 PM, Erich Steinböck wrote:     errArr=.array~new     address system 'some command' with error using (errArr) With our new twinkle smiley

Re: [Oorexx-devel] ooRexx /dev/null for redirected command handler

I was going to suggest address system 'some command' with error using (.array~new) but I like your answer better :-) Gil PS. This should also work address system 'some command' with error stream 'nul:' On 12/3/2022 2:39 PM, Erich Steinböck wrote:     errArr=.array~new    

Re: [Oorexx-devel] Ad "portable" versions of ooRexx

On Windows, one normally runs NMAKE to build ooRexx.  Is that the case for the portable version as well? I.e. after running CMAKE and NMAKE to do the build, would one then run "NMAKE portable" to create the two zip files? Gil On 8/3/2022 7:39 AM, Rony G. Flatscher wrote: Commited with

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

ESS command for Windows but cURL should be there. Given that the version only changes approximately once a year it might stop working before the next version, not sure if it is really necessary to check for the latest version? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se Am 08.07.

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

he current level is.  (Used to be called "screen scraping" back in the day.)    Gil On 7/8/2022 8:55 AM, Rony G. Flatscher wrote: On 08.07.2022 14:38, Gilbert Barmwater wrote: Thanks Rony.  I will see where the copyright statement is coming from and make the change.  I'm going

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

to determine what the current level of Apache Fop is.  If interested, please contact me either on- or off-list.  Thanks. GB On 7/8/2022 8:00 AM, Rony G. Flatscher wrote: Hi Gil, On 07.07.2022 22:10, Gilbert Barmwater wrote: I have now downloaded fop-2.7 and used it successfully to build

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

: Gil, thank you very much fir your detailed explanations, very much appreciated! Best regards —-rony Rony G. Flatscher (mobil/e) Am 06.07.2022 um 02:48 schrieb Gilbert Barmwater :  OK, I have some time now so here are the details (see below). Gil On 7/5/2022 8:54 AM, Gilbert Barmwater

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

OK, I have some time now so here are the details (see below). Gil On 7/5/2022 8:54 AM, Gilbert Barmwater wrote: Thanks, Rony, for taking a look at the document build package I recently uploaded and for your initial feedback.  I hope to be able to provide a detailed response later today

Re: [Oorexx-devel] First impressions of "bldoc_orx" on Windows

Thanks, Rony, for taking a look at the document build package I recently uploaded and for your initial feedback.  I hope to be able to provide a detailed response later today or tomorrow. Gil On 7/5/2022 6:10 AM, Rony G. Flatscher wrote: Hi Gil, thank you for providing the ooRexx set of

Re: [Oorexx-devel] Generating the documentation: removing "Common_Content"?

On 7/2/2022 3:07 PM, Gilbert Barmwater wrote: On 7/2/2022 2:48 PM, Rony G. Flatscher wrote: When creating a pdf book the current script "docprep.cmd" copies the files from "oorexx/trunc/oorexx/en-US" to "oorexx/trunc/{book}/en-US/Commons_Content". Not sure

Re: [Oorexx-devel] Generating the documentation: removing "Common_Content"?

On 7/2/2022 2:48 PM, Rony G. Flatscher wrote: When creating a pdf book the current script "docprep.cmd" copies the files from "oorexx/trunc/oorexx/en-US" to "oorexx/trunc/{book}/en-US/Commons_Content". Not sure why this happens as it should be possible to refer to "oorexx/en-US" files with

Re: [Oorexx-devel] Ad current documentation version and revission information on the front and second page

On 7/2/2022 2:35 PM, Rony G. Flatscher wrote: While probing downloading of the latest documentation files I noticed that there are places that probably need some automated update in the process of generating new versions of the documentation, e.g.: rexxref.pdf has the following lines on

Re: [Oorexx-devel] Documentation build

Thanks Rick!  I knew there was a way to tell the installer build where to get the PDFs but couldn't remember how. Gil On 6/28/2022 2:58 PM, Rick McGuire wrote: On Tue, Jun 28, 2022 at 1:58 PM Gilbert Barmwater wrote: Thanks P.O., they look great!  Now one more issue to address

Re: [Oorexx-devel] Documentation build

Thanks P.O., they look great!  Now one more issue to address. As you know, the Windows build includes the documentation and the user has the option of installing it as part of installing ooRexx.  Currently, the PDFs in the Windows builds are NOT the ones you generate.  I have never done an

Re: [Oorexx-devel] ooRexx Testing

I found this on my system for what it's worth.  Apparently it was posted somewhere by Walter in the dim past. "Developing ooRexx Test Cases This cookbook documents my hard way to getting rid of my first contributions to the testing of 5.0.0. It's for Windows only, 1) Download SVN if you

Re: [Oorexx-devel] ooRexx 5.0 GA

I agree it should work. RC(30) means the command environment is unknown.  I see that you have "address pipe ..." so that may be the problem.  You might try "address path pipe..." or "address '' pipe..." and see if that works any better. Gil On 6/22/2022 10:19 AM, René Jansen wrote: I think

Re: [Oorexx-devel] ooRexx 5.0 GA

I checked the documentation and it isn't really clear (to me). So I ran rexxtry and got: address cmd with output stem d   Oooops ! ... try again. Symbol expected.   Stem symbol expected after STEM keyword.   rc = 20.932 ... rexxtry.rex

Re: [Oorexx-devel] A request ad documentation on how to create the documentation ...

Hi Rony, This link should explain where the tools are for both Windows, Mac and Ubuntu.  If you have done a checkout or update of the docs, you should already have them!  I defer to PO to expound on the status re

Re: [Oorexx-devel] Windows Installers

I just noticed a new series of builds have been uploaded and they still seem to contain the redundant installers for Windows.  Did the disable not work? Gil On 4/12/2022 11:03 AM, P.O. Jonsson wrote: I will disable the uploads of the redundant installers, 8 -> 2 but I do not dare touching

Re: [Oorexx-devel] Building the documentation for ooRexx on Jenkins

On 2/21/2022 5:36 PM, P.O. Jonsson wrote: Does anyone remember what this setting is for in the build step for the documentation? :-- list change sets curl %BUILD_URL%api/json With Jenkins upgraded from http:// to https:// this seems to generate an error jenkins@DELLGX760

Re: [Oorexx-devel] What am I missing?

nice flow of control trace for the package. Rick On Sun, Feb 6, 2022 at 12:17 PM Gilbert Barmwater wrote: Before I open a documentation bug on this, I have a question.  Is there a reason the enhancement to TRACE L was only done for ::OPTIONS TRACE and not for the TRACE keyword

Re: [Oorexx-devel] What am I missing?

, Gilbert Barmwater wrote: OK, that explains it, thanks.  Should I open a documentation bug? On 2/5/2022 4:09 AM, Erich Steinböck wrote: Hi Gil, rexxref could be clearer here. When specified with the TRACE keyword instruction, trace option L traces internal labels only. When specified

Re: [Oorexx-devel] What am I missing?

OK, that explains it, thanks.  Should I open a documentation bug? On 2/5/2022 4:09 AM, Erich Steinböck wrote: Hi Gil, rexxref could be clearer here. When specified with the TRACE keyword instruction, trace option L traces internal labels only. When specified with the ::OPTIONS directive, as a

[Oorexx-devel] What am I missing?

The recent post by Terry Fuller inspired me to explore the "trace L" option which the documentation says "Traces method and routine invocations, internal subroutine calls, transfers of control because of the SIGNAL instruction, and labels passed during program execution." Since I hadn't ever

Re: [Oorexx-devel] SysTextScreenRead

and fix! Gil On 12/14/2021 3:59 PM, Gilbert Barmwater wrote: OK, I'll get a new build and validate in my environment. Thanks! On 12/14/2021 2:04 PM, Rick McGuire wrote: I just committed a fix for this issue. Rick On Tue, Dec 14, 2021 at 11:38 AM Gil Barmwater wrote: Do we have any

Re: [Oorexx-devel] SysTextScreenRead

OK, I'll get a new build and validate in my environment.  Thanks! On 12/14/2021 2:04 PM, Rick McGuire wrote: I just committed a fix for this issue. Rick On Tue, Dec 14, 2021 at 11:38 AM Gil Barmwater wrote: Do we have any test for the subject function and are they working as

[Oorexx-devel] SysTextScreenRead

Do we have any test for the subject function and are they working as expected?  It seems that when I try "screen = SysTextScreenRead(0, 0)" as per the example in the reference, I always get an error 40.1.  However, adding a length as the third argument makes it work. Gil B.

[Oorexx-devel] SF certificate errors

It has been a while since I updated my working copy of ooRexx but when I tried to do so recently, I received a Certificate error message.� Anyone else seeing this?� Is it safe to ignore? Gil B. ___ Oorexx-devel mailing list