https://sourceforge.net/p/oorexx/documentation/2026-04-14T21:29:09.466000ZRecent changes to documentation2026-04-14T21:29:09.466000Z2026-04-14T21:29:09.466000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net13b7de04c06d42a90cf50442de67a33c83766529

<div class="markdown_content"><p>I was able to get the zip file, open it (Windows treats it as a folder), and double click on the readme.pdf. Adobe Reader was able to display the document which looked normal and complete. So I have no idea why you would not be able to upload it to SF. Sorry :-(</p></div>

2026-04-14T19:30:57.386000Z2026-04-14T19:30:57.386000ZRony G. Flatscherhttps://sourceforge.net/u/orexx/https://sourceforge.netb89ff0558c28e3225c384fe30ffa200b7eec45e6

<div class="markdown_content"><p>+1 (deprecate note in bldoc_win)</p></div>

2026-04-14T16:02:58.863000Z2026-04-14T16:02:58.863000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net4ba7bc0b2cd5f140f2f17fb30e5bf98f17cde3e0

<div class="markdown_content"><p>I will have a look at the zip file later today. No changes needed to HTML, this fix only affects the PDFs.</p></div>

2026-04-14T15:59:47.469000Z2026-04-14T15:59:47.469000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net9dc2994b102fbc4ca63889577e3e4371cd50b48a

<div class="markdown_content"><p>I don't recall the last time I updated bldoc_win as it really is now redundant. Perhaps a note in that folder that it is deprecated and the bldoc_orx should be used instead. Thoughts?</p></div>

2026-04-13T15:26:59.358000Z2026-04-13T15:26:59.358000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.nete25dabe758d8253e931cc8f94040bef420bf9c8b

<div class="markdown_content"><p>All documents built successfully on my Windows 10 machine. Fix committed with Revision: 13146</p></div>

2026-04-11T21:31:45.275000Z2026-04-11T21:31:45.275000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net5debbf7aa917dce15992887b84e483deeeb603fd

<div class="markdown_content"><p>Yes, I will do that. The only (operational) file affected is pdf.xsl which you will need to update (from SF) on your Mac before you kick off the document builds. Stay tuned.</p></div>

2026-04-11T19:19:45.160000Z2026-04-11T19:19:45.160000ZJosep Maria Blascohttps://sourceforge.net/u/jmblasc2/https://sourceforge.neta2edf7c5d35a5f940956245281d18b2589a1c1be

<div class="markdown_content"><p>No reason at all, Gil. Go ahead. And thank you!</p></div>

2026-04-11T19:10:42.288000Z2026-04-11T19:10:42.288000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net7eb003739023caeb052b049531c4c11ae1be8175

<div class="markdown_content"><p>I understand. Just for "fun" I built the RexxRef PDF using your modifed pdf.xsl and it looked fine to me. I am happy to commit it so that the upcoming release of 5.2.0 will have the benefit of this fix even if you develop a "better" one later on. Let me know if you have any reasons why I shouldn't do that. </p></div>

2026-04-11T11:24:49.861000Z2026-04-11T11:24:49.861000ZJosep Maria Blascohttps://sourceforge.net/u/jmblasc2/https://sourceforge.net9d989c1f5f34b637e083dfa8f38882b5f5369a2d

<div class="markdown_content"><p>Thanks for the explanations, Gil. If nobody beats me to it, I'll implement the 1.79.2 route, but this will have to wait until the Barcelona Symposium is over.</p></div>

2026-04-10T17:34:25.785000Z2026-04-10T17:34:25.785000ZGil Barmwaterhttps://sourceforge.net/u/orange-e/https://sourceforge.net1ef3fab6343fe4887cb41cde826bda708aeb1b3b

<div class="markdown_content"><p>In general, I agree that returning self as opposed to returning nothing will make chaining easier and avoid the error of not using double-~ when chaining is desired. Howver, in this case, the idea is to create a "stand alone" functionality - reading/writing an entire file's worth of lines - so returning 'self' (which in this case would be the .file class) is not particularly useful. It might be good to return 0 however, in order to maintain compatibility with the arrayOut method of the stream class.</p></div>