[Oorexx-devel] Script (Re: Ad CHANGES

2022-12-19 Thread Rony G. Flatscher 

On 19.12.2022 19:23, P.O. Jonsson wrote:
Would it be much work to indicate who created the bug report/rfe ? I guess I can look at my own at 
sourceforge but it would be convenient to have


It is work and unfortunately my time buffers are vaporizing a little bit.

In principle everything that is listed and can be parsed from 
 can be incorporated. However, CHANGES is a 
brief, scarce text file and does not have too much space, hence having too much of information will 
make it unreadable.


Enclosed a coarsely cleansed version of the (quick & dirty) script (needing maybe a little bit more 
documentation) that can be changed/edited as much as the heart wants it too! ;)


Of course, one needs ooRexx 5.0.0 to run it :) (and only tested on Windows at the moment but should 
work on Unixes as well).


---rony
pkgLocal=.context~package~local
pkgLocal~null.Dev=.nullDevice~new

ticketTypes="bugs","feature-requests","documentation","patches"
pkgLocal~shortNames=.stringTable~of(("bugs","BUG"), -
("feature-requests","RFE"), -
("documentation"   ,"DOC"), -
("patches" ,"PAT"))
proj   ="p/oorexx/"
host   ="https://sourceforge.net/;
query  ="/search/?q=status%3Aaccepted+or+status%3Apending"

outArr=.array~new-- array for result

do label types counter c1 t over ticketTypes
   resArr=.array~new
   say c1"." pp(t)
   cmd=host || proj || t || query
   address system "curl -L" cmd with output using (outArr) error using (.null.dev)
   str=outArr~makeString

   parse var str '' '' ''
   currPage=1
   needle=''nr  ''  -
(needle)  '/">'summary ''  -
'' status ''  str

  if nr="" then  -- no more entries, read next page, if any
  do
  currPage+=1
  if currPage>lastPage then leave group
  cmdPage=quote(cmd || "=" || (currPage-1))  -- 0-based pages
  address system "curl -L" cmdPage with output using (outArr) error using (.null.dev)
  str=outArr~makeString
  iterate group
  end
  summary=unEsc(summary)
  resArr~append(.ticket~new(t,nr,summary,status))
   end
   resArr=resArr~sort
   say
   say "sorted:"
   do counter c3 i over resArr
  say c3~right(4)":" i
   end
   say "-*-*"~copies(25)
   say
end

/* * */
::routine pp
  return "["arg(1)"]"

/* * */
::routine unEsc
  parse arg val
  val=val~strip
  mb=.mutableBuffer~new
  do while val<>""
parse var val before

Re: [Oorexx-devel] Ad CHANGES

2022-12-19 Thread P.O. Jonsson 
Would it be much work to indicate who created the bug report/rfe ? I guess I 
can look at my own at sourceforge but it would be convenient to have

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 19.12.2022 um 18:58 schrieb Rony G. Flatscher :
> 
> Had a hard time but finally managed to get a little ooRexx 5.0 script to 
> read, sort and format the current four ticket groups to match the order in 
> the current CHANGES file. 
> 
> The idea is to use the output to replace the current list of tickets that are 
> pending or accepted, but have everyone here take a look at it as for debug 
> purposes the output gets temporarily a counter and a group id:
> 
> 1. [bugs]
> 
> sorted:
>1: BUG # 1853 CMake breaks when no CMAKE_BUILD_TYPE specified
>2: BUG # 1848 NUMERIC FUZZ not respected for integer comparisons
>3: BUG # 1846 RAISE PROPAGATE for NOMETHOD not using correct message form
>4: BUG # 1845 ooRexx CMake Build Error -- Linux ARM aarch64 and armv7l 
> Architectures
>5: BUG # 1842 linein performance issue
>6: BUG # 1834 Invalid .Error destination crashes interpreter
>7: BUG # 1830 Performance problems with lines()
>8: BUG # 1829 TEST_REPLY_CONCURRENT test failing on OpenIndiana
>9: BUG # 1827 13 Sample files missing shebang
>   10: BUG # 1822 Expanding multi-dimensional Arrays changes content
>   11: BUG # 1821 OLEVariant not honored for VT_ARRAY,VT_R8 for AutoCAD
>   12: BUG # 1820 OLEObject: (HRESULT=80010001 "Call was rejected by callee.")
>   13: BUG # 1819 Crash in OLEObject: hResult=0x80010001 [Call was rejected by 
> callee.]
>   14: BUG # 1818 samples/windows/ole/adsi3.rex does not work on non-English 
> systems
>   15: BUG # 1817 Memory alloc/free should always match
>   16: BUG # 1816 Multiple rxapi instances
>   17: BUG # 1814 CPack FREEBSD generator not available for FreeBSD
>   18: BUG # 1812 ooDialog Guide Sample Exercise08 - Drag and Drop doesn't work
>   19: BUG # 1810 CMake CMAKE_CXX_CREATE_SHARED_MODULE issue
>   20: BUG # 1806 Wrongly stating "Error 15.5: Hexadecimal strings must be 
> grouped..."
>   21: BUG # 1805 newFile method's context arg doesn't default to PROGRAMSCOPE
>   22: BUG # 1802 TIME bif fails when offset specified
>   23: BUG # 1800 lastModified one day off on New Year's Day on Linux
>   24: BUG # 1799 cpack and absolute installation paths
>   25: BUG # 1798 SysTextScreenRead() fails when reading more that 16000 
> characters
>   26: BUG # 1795 Invalid objects detected during garbage collection running 
> the test suite.
>   27: BUG # 1794 testsuite just dies
>   28: BUG # 1791 rexxapitypes.h includes for stdint.h and inttypes.h not 
> updated for external application builds with newer compilers
>   29: BUG # 1790 uppercase issue on NetBSD
>   30: BUG # 1788 .RexxInfo~executable not working for NetBSD and OpenBSD
>   31: BUG # 1787 .socket~gethostid() method and SockGetHostId() function not 
> working correctly on all platforms; rxsockfn.cpp may need revising
>   32: BUG # 1786 RexxPullFromQueue() returning invalid data for a null queue 
> entry
>   33: BUG # 1784 r12299 - homebrew quirks
>   34: BUG # 1777 rc = SockSetSockOpt(socket, SOL_SOCKET, SO_RCVTIMEO, 3000) 
> receives -1 rc and fails to timout on Linux
>   35: BUG # 1776 SysFileXXX.testGroup SysDrive.testGroup causing syntax 
> errors on Windows 7 and 8
>   36: BUG # 1774 Building and Testing on Windows 8
>   37: BUG # 1771 Stream's 'arrayin' does not return array object
>   38: BUG # 1770 SysSemaphore sets invalid priority/policy
>   39: BUG # 1769 REXX_PATH default always set
>   40: BUG # 1768 ncurses.cls doesn't build on some platforms
>   41: BUG # 1766 rexximage cleanup: removeClassMethod forgets some classes
>   42: BUG # 1763 StreamSocket issues
>   43: BUG # 1758 rxunixsys xattr functions are not built
>   44: BUG # 1757 Floating-point conversions give incorrect results when not 
> run in C locale
>   45: BUG # 1754 Install of RPM ooRexx-5.0.0-12217.x86_64 fails.
>   46: BUG # 1753 oodialog sample toolTip.rex crashes
>   47: BUG # 1751 INTERPRET wipes out its parent's StackFrame name
>   48: BUG # 1750 INTERPRET .context~digits different from digits()
>   49: BUG # 1748 Typo in faux pthread_mutex_timedlock
>   50: BUG # 1746 REQUIRES doesn't find its file if it starts with a dot
>   51: BUG # 1745 SysSearchPath finds files starting with dot when it should 
> not
>   52: BUG # 1742 Stream RECLENGTH 1 issues
>   53: BUG # 1738 Inconsistent tracing of DO loops
>   54: BUG # 1734 Hang with multiple threads
>   55: BUG # 1730 Error message insert off by one
>   56: BUG # 1728 Hang condition on Windows
>   57: BUG # 1727 216 warnings building ooRexx with clang 11
>   58: BUG # 1724 File attributes for Windows system files cannot be read
>   59: BUG # 1723 Correct case-sensitivity methods
>   60: BUG # 1721 R5 linein/lineout DRAMATIC slowdown???
>   61: BUG # 1719 Sysfiletree does not handle ";"s properly
>   62: BUG # 1718 EXTERNAL option issues
>   63: BUG

[Oorexx-devel] Ad CHANGES

2022-12-19 Thread Rony G. Flatscher 
Had a hard time but finally managed to get a little ooRexx 5.0 script to read, sort and format the 
current four ticket groups to match the order in the current CHANGES file.


The idea is to use the output to replace the current list of tickets that are pending or accepted, 
but have everyone here take a look at it as for debug purposes the output gets temporarily a counter 
and a group id:


   1. [bugs]

   sorted:
   1: BUG # 1853 CMake breaks when no CMAKE_BUILD_TYPE specified
   2: BUG # 1848 NUMERIC FUZZ not respected for integer comparisons
   3: BUG # 1846 RAISE PROPAGATE for NOMETHOD not using correct message form
   4: BUG # 1845 ooRexx CMake Build Error -- Linux ARM aarch64 and armv7l 
Architectures
   5: BUG # 1842 linein performance issue
   6: BUG # 1834 Invalid .Error destination crashes interpreter
   7: BUG # 1830 Performance problems with lines()
   8: BUG # 1829 TEST_REPLY_CONCURRENT test failing on OpenIndiana
   9: BUG # 1827 13 Sample files missing shebang
  10: BUG # 1822 Expanding multi-dimensional Arrays changes content
  11: BUG # 1821 OLEVariant not honored for VT_ARRAY,VT_R8 for AutoCAD
  12: BUG # 1820 OLEObject: (HRESULT=80010001 "Call was rejected by 
callee.")
  13: BUG # 1819 Crash in OLEObject: hResult=0x80010001 [Call was rejected 
by callee.]
  14: BUG # 1818 samples/windows/ole/adsi3.rex does not work on non-English 
systems
  15: BUG # 1817 Memory alloc/free should always match
  16: BUG # 1816 Multiple rxapi instances
  17: BUG # 1814 CPack FREEBSD generator not available for FreeBSD
  18: BUG # 1812 ooDialog Guide Sample Exercise08 - Drag and Drop doesn't 
work
  19: BUG # 1810 CMake CMAKE_CXX_CREATE_SHARED_MODULE issue
  20: BUG # 1806 Wrongly stating "Error 15.5: Hexadecimal strings must be 
grouped..."
  21: BUG # 1805 newFile method's context arg doesn't default to 
PROGRAMSCOPE
  22: BUG # 1802 TIME bif fails when offset specified
  23: BUG # 1800 lastModified one day off on New Year's Day on Linux
  24: BUG # 1799 cpack and absolute installation paths
  25: BUG # 1798 SysTextScreenRead() fails when reading more that 16000 
characters
  26: BUG # 1795 Invalid objects detected during garbage collection running 
the test suite.
  27: BUG # 1794 testsuite just dies
  28: BUG # 1791 rexxapitypes.h includes for stdint.h and inttypes.h not 
updated for external application builds with newer compilers
  29: BUG # 1790 uppercase issue on NetBSD
  30: BUG # 1788 .RexxInfo~executable not working for NetBSD and OpenBSD
  31: BUG # 1787 .socket~gethostid() method and SockGetHostId() function 
not working correctly on all platforms; rxsockfn.cpp may need revising
  32: BUG # 1786 RexxPullFromQueue() returning invalid data for a null 
queue entry
  33: BUG # 1784 r12299 - homebrew quirks
  34: BUG # 1777 rc = SockSetSockOpt(socket, SOL_SOCKET, SO_RCVTIMEO, 3000) 
receives -1 rc and fails to timout on Linux
  35: BUG # 1776 SysFileXXX.testGroup SysDrive.testGroup causing syntax 
errors on Windows 7 and 8
  36: BUG # 1774 Building and Testing on Windows 8
  37: BUG # 1771 Stream's 'arrayin' does not return array object
  38: BUG # 1770 SysSemaphore sets invalid priority/policy
  39: BUG # 1769 REXX_PATH default always set
  40: BUG # 1768 ncurses.cls doesn't build on some platforms
  41: BUG # 1766 rexximage cleanup: removeClassMethod forgets some classes
  42: BUG # 1763 StreamSocket issues
  43: BUG # 1758 rxunixsys xattr functions are not built
  44: BUG # 1757 Floating-point conversions give incorrect results when not 
run in C locale
  45: BUG # 1754 Install of RPM ooRexx-5.0.0-12217.x86_64 fails.
  46: BUG # 1753 oodialog sample toolTip.rex crashes
  47: BUG # 1751 INTERPRET wipes out its parent's StackFrame name
  48: BUG # 1750 INTERPRET .context~digits different from digits()
  49: BUG # 1748 Typo in faux pthread_mutex_timedlock
  50: BUG # 1746 REQUIRES doesn't find its file if it starts with a dot
  51: BUG # 1745 SysSearchPath finds files starting with dot when it should 
not
  52: BUG # 1742 Stream RECLENGTH 1 issues
  53: BUG # 1738 Inconsistent tracing of DO loops
  54: BUG # 1734 Hang with multiple threads
  55: BUG # 1730 Error message insert off by one
  56: BUG # 1728 Hang condition on Windows
  57: BUG # 1727 216 warnings building ooRexx with clang 11
  58: BUG # 1724 File attributes for Windows system files cannot be read
  59: BUG # 1723 Correct case-sensitivity methods
  60: BUG # 1721 R5 linein/lineout DRAMATIC slowdown???
  61: BUG # 1719 Sysfiletree does not handle ";"s properly
  62: BUG # 1718 EXTERNAL option issues
  63: BUG # 1717 ooDialog FileNameDialog issue
  64: BUG # 1716 .method and .routine "new" method cannot process encoded 
compiled programs
  65: BUG # 1715

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

2022-12-19 Thread Gilbert Barmwater 

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 come out of the trunk version.

We didn't start using them until Erich took over updating the docs in 
5.0.0.


Rick

Gil

On 12/19/2022 10:22 AM, Rick McGuire wrote:

No, the flags should still be there. Those are for the benefit 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 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 is running without problem.

Gil

On 12/19/2022 8:37 AM, ooRexx wrote:
>> On 19. Dec 2022, at 11:23, Rony G. Flatscher
 wrote:
>>
>> Dear P.O.,
>>
>> On 18.12.2022 22:42, ooRexx wrote:
>>> Regarding the documentation I have merged 5.0.0html and
5.0.0beta into 5.0.0beta and then copied all into
5.0.0_Release_Candidate. Everything amended from this point
on should arrive in 5.0.0_Release_Candidate only.
>> great, thank you very much!
>>
>> Would it be possible to rename the zip-files such that
they end in "-html.zip" as was done for 4.2.0, e.g. instead
of "rexxref.zip" it should read "rexxref-html.zip"?
> I have done that, both for 5.0.0beta and for
5.0.0_Release_Candidate. I amended the build scripts so that
for the future it will stay like that.
>
> At the same time I removed rexxgtk from the documentation.
It will also not be built in the future; it you want to
revive it let me know and I will add it again.
>
>> This way it is clear for the uninitiated that the
zip-archives contain the html-rendering of the documentation
as opposed to the pdf-files ("rexxref.pdf").
>>
>> ---
>>
>> @Terry: in the context of rehauling the oorexx.org
 page we could make all the
html-documentation available from that site which eventually
would make it possible to hit the ooRexx documentation via
search engines.
>>
>> ---rony
>>
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread Rick McGuire 
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
> come out of the trunk version.
>
We didn't start using them until Erich took over updating the docs in
5.0.0.

Rick



> Gil
> On 12/19/2022 10:22 AM, Rick McGuire wrote:
>
> No, the flags should still be there. Those are for the benefit 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 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 is running without problem.
>>
>> Gil
>>
>> On 12/19/2022 8:37 AM, ooRexx wrote:
>> >> On 19. Dec 2022, at 11:23, Rony G. Flatscher 
>> wrote:
>> >>
>> >> Dear P.O.,
>> >>
>> >> On 18.12.2022 22:42, ooRexx wrote:
>> >>> Regarding the documentation I have merged 5.0.0html and 5.0.0beta
>> into 5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything
>> amended from this point on should arrive in 5.0.0_Release_Candidate only.
>> >> great, thank you very much!
>> >>
>> >> Would it be possible to rename the zip-files such that they end in
>> "-html.zip" as was done for 4.2.0, e.g. instead of "rexxref.zip" it should
>> read "rexxref-html.zip"?
>> > I have done that, both for 5.0.0beta and for 5.0.0_Release_Candidate. I
>> amended the build scripts so that for the future it will stay like that.
>> >
>> > At the same time I removed rexxgtk from the documentation. It will also
>> not be built in the future; it you want to revive it let me know and I will
>> add it again.
>> >
>> >> This way it is clear for the uninitiated that the zip-archives contain
>> the html-rendering of the documentation as opposed to the pdf-files
>> ("rexxref.pdf").
>> >>
>> >> ---
>> >>
>> >> @Terry: in the context of rehauling the oorexx.org page we could make
>> all the html-documentation available from that site which eventually would
>> make it possible to hit the ooRexx documentation via search engines.
>> >>
>> >> ---rony
>> >>
>> >>
>> >>
>> >> ___
>> >> Oorexx-devel mailing list
>> >> Oorexx-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> >
>> >
>> > ___
>> > Oorexx-devel mailing list
>> > Oorexx-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
>
> ___
> Oorexx-devel mailing 
> listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread Gilbert Barmwater 
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 come out of the trunk version.


Gil

On 12/19/2022 10:22 AM, Rick McGuire wrote:
No, the flags should still be there. Those are for the benefit 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 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 is running without problem.

Gil

On 12/19/2022 8:37 AM, ooRexx wrote:
>> On 19. Dec 2022, at 11:23, Rony G. Flatscher
 wrote:
>>
>> Dear P.O.,
>>
>> On 18.12.2022 22:42, ooRexx wrote:
>>> Regarding the documentation I have merged 5.0.0html and
5.0.0beta into 5.0.0beta and then copied all into
5.0.0_Release_Candidate. Everything amended from this point on
should arrive in 5.0.0_Release_Candidate only.
>> great, thank you very much!
>>
>> Would it be possible to rename the zip-files such that they end
in "-html.zip" as was done for 4.2.0, e.g. instead of
"rexxref.zip" it should read "rexxref-html.zip"?
> I have done that, both for 5.0.0beta and for
5.0.0_Release_Candidate. I amended the build scripts so that for
the future it will stay like that.
>
> At the same time I removed rexxgtk from the documentation. It
will also not be built in the future; it you want to revive it let
me know and I will add it again.
>
>> This way it is clear for the uninitiated that the zip-archives
contain the html-rendering of the documentation as opposed to the
pdf-files ("rexxref.pdf").
>>
>> ---
>>
>> @Terry: in the context of rehauling the oorexx.org
 page we could make all the html-documentation
available from that site which eventually would make it possible
to hit the ooRexx documentation via search engines.
>>
>> ---rony
>>
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] sorry about recreating docs/branches/5.0.0

2022-12-19 Thread Rony G. Flatscher 
Hi there, sorry, did not see "docs/branches/5.0.0" and thought I forgot it so created it. The 
reasone being that I did not do an "svn update" from the root. :(


Hope that no one got affected by this inadvertently.

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread Rick McGuire 
No, the flags should still be there. Those are for the benefit 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 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 is running without problem.
>
> Gil
>
> On 12/19/2022 8:37 AM, ooRexx wrote:
> >> On 19. Dec 2022, at 11:23, Rony G. Flatscher 
> wrote:
> >>
> >> Dear P.O.,
> >>
> >> On 18.12.2022 22:42, ooRexx wrote:
> >>> Regarding the documentation I have merged 5.0.0html and 5.0.0beta into
> 5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything
> amended from this point on should arrive in 5.0.0_Release_Candidate only.
> >> great, thank you very much!
> >>
> >> Would it be possible to rename the zip-files such that they end in
> "-html.zip" as was done for 4.2.0, e.g. instead of "rexxref.zip" it should
> read "rexxref-html.zip"?
> > I have done that, both for 5.0.0beta and for 5.0.0_Release_Candidate. I
> amended the build scripts so that for the future it will stay like that.
> >
> > At the same time I removed rexxgtk from the documentation. It will also
> not be built in the future; it you want to revive it let me know and I will
> add it again.
> >
> >> This way it is clear for the uninitiated that the zip-archives contain
> the html-rendering of the documentation as opposed to the pdf-files
> ("rexxref.pdf").
> >>
> >> ---
> >>
> >> @Terry: in the context of rehauling the oorexx.org page we could make
> all the html-documentation available from that site which eventually would
> make it possible to hit the ooRexx documentation via search engines.
> >>
> >> ---rony
> >>
> >>
> >>
> >> ___
> >> Oorexx-devel mailing list
> >> Oorexx-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> >
> >
> > ___
> > Oorexx-devel mailing list
> > Oorexx-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Ad *CHG* and *NEW* markup in docs (Re: docs Re: Ad current release 5.0.0

2022-12-19 Thread Rony G. Flatscher 

On 19.12.2022 16:12, Gilbert Barmwater wrote:
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 
is running without problem.


hmm, personally I would find it helpful as 4.2 user to see in the documentation what is new and what 
got changed in 5.0.0, so I would suggest to leave it as is.


However, we could remove those two strings for the documentation for 5.1.0 and instead use *CHG* and 
*NEW* for those features in 5.1.0 such that the 5.0.0 users would be able to see at a glance what 
got changed and what is new there. Then for 5.2.0 they get evaporated and the changed and new 
features of 5.2.0 would get marked and so forth.


What would you think?

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread Gilbert Barmwater 
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 is running without problem.


Gil

On 12/19/2022 8:37 AM, ooRexx wrote:

On 19. Dec 2022, at 11:23, Rony G. Flatscher  wrote:

Dear P.O.,

On 18.12.2022 22:42, ooRexx wrote:

Regarding the documentation I have merged 5.0.0html and 5.0.0beta into 
5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything amended 
from this point on should arrive in 5.0.0_Release_Candidate only.

great, thank you very much!

Would it be possible to rename the zip-files such that they end in "-html.zip" as was done for 
4.2.0, e.g. instead of "rexxref.zip" it should read "rexxref-html.zip"?

I have done that, both for 5.0.0beta and for 5.0.0_Release_Candidate. I amended 
the build scripts so that for the future it will stay like that.

At the same time I removed rexxgtk from the documentation. It will also not be 
built in the future; it you want to revive it let me know and I will add it 
again.


This way it is clear for the uninitiated that the zip-archives contain the html-rendering 
of the documentation as opposed to the pdf-files ("rexxref.pdf").

---

@Terry: in the context of rehauling the oorexx.org page we could make all the 
html-documentation available from that site which eventually would make it 
possible to hit the ooRexx documentation via search engines.

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread ooRexx 
> On 19. Dec 2022, at 11:23, Rony G. Flatscher  wrote:
> 
> Dear P.O.,
> 
> On 18.12.2022 22:42, ooRexx wrote:
>> Regarding the documentation I have merged 5.0.0html and 5.0.0beta into 
>> 5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything 
>> amended from this point on should arrive in 5.0.0_Release_Candidate only.
> 
> great, thank you very much!
> 
> Would it be possible to rename the zip-files such that they end in 
> "-html.zip" as was done for 4.2.0, e.g. instead of "rexxref.zip" it should 
> read "rexxref-html.zip"?

I have done that, both for 5.0.0beta and for 5.0.0_Release_Candidate. I amended 
the build scripts so that for the future it will stay like that.

At the same time I removed rexxgtk from the documentation. It will also not be 
built in the future; it you want to revive it let me know and I will add it 
again.

> 
> This way it is clear for the uninitiated that the zip-archives contain the 
> html-rendering of the documentation as opposed to the pdf-files 
> ("rexxref.pdf").
> 
> ---
> 
> @Terry: in the context of rehauling the oorexx.org page we could make all the 
> html-documentation available from that site which eventually would make it 
> possible to hit the ooRexx documentation via search engines.
> 
> ---rony
> 
> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] "rexxgtk" and release 5.0.0

2022-12-19 Thread Rick McGuire 
+1

On Mon, Dec 19, 2022 at 5:53 AM Rony G. Flatscher 
wrote:

> There is a current question on
> "
> https://sourceforge.net/p/oorexx/discussion/general/thread/94d8616a49/?limit=25#19b3;
> about rexxgtk
> being included or not in the release.
>
> The documentation "rexxgtk.pdf" gets installed on my PC and in its
> installation section describes
> Linux and Windows. One is supposed to '::requires "rexxgtk.cls"' to get
> access to it, however there
> is no "librexxgtk.so" on my Ubuntu Linux nor "librexxgtk.dll" on Windows.
>
> AFAIK originally this library got created by David Ashley, but I have no
> memory about anyone else
> having worked on it or what its state would be.
>
> As such I would propose to not install "rexxgtk.pdf" as the missing
> shared/dynamic library does not
> get installed either in the ooRexx 5.0.0 release.
>
> What do you think?
>
> ---rony
>
> P.S.: As gtk is doubtlessly important it would be great if some of the
> Unix gurus would look into
> it, check out the code and state and advice.
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] "rexxgtk" and release 5.0.0

2022-12-19 Thread Rony G. Flatscher 
There is a current question on 
"https://sourceforge.net/p/oorexx/discussion/general/thread/94d8616a49/?limit=25#19b3; about rexxgtk 
being included or not in the release.


The documentation "rexxgtk.pdf" gets installed on my PC and in its installation section describes 
Linux and Windows. One is supposed to '::requires "rexxgtk.cls"' to get access to it, however there 
is no "librexxgtk.so" on my Ubuntu Linux nor "librexxgtk.dll" on Windows.


AFAIK originally this library got created by David Ashley, but I have no memory about anyone else 
having worked on it or what its state would be.


As such I would propose to not install "rexxgtk.pdf" as the missing shared/dynamic library does not 
get installed either in the ooRexx 5.0.0 release.


What do you think?

---rony

P.S.: As gtk is doubtlessly important it would be great if some of the Unix gurus would look into 
it, check out the code and state and advice.



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

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

2022-12-19 Thread Rony G. Flatscher 

Dear P.O.,

On 18.12.2022 22:42, ooRexx wrote:

Regarding the documentation I have merged 5.0.0html and 5.0.0beta into 
5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything amended 
from this point on should arrive in 5.0.0_Release_Candidate only.


great, thank you very much!

Would it be possible to rename the zip-files such that they end in "-html.zip" as was done for 
4.2.0, e.g. instead of "rexxref.zip" it should read "rexxref-html.zip"?


This way it is clear for the uninitiated that the zip-archives contain the html-rendering of the 
documentation as opposed to the pdf-files ("rexxref.pdf").


---

@Terry: in the context of rehauling the oorexx.org page we could make all the html-documentation 
available from that site which eventually would make it possible to hit the ooRexx documentation via 
search engines.


---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Ad current release 5.0.0

2022-12-19 Thread Rony G. Flatscher 

On 18.12.2022 22:06, ooRexx wrote:

I have great news from down-under

Mark Hessling just confirmed that he could build and test the latest ooRexx 
flawlessly on M1 Mac. Here the result

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 19 Dec 2022
OS Name:DARWIN
SysVersion: Darwin 21.6.0

Tests ran:  23878
Assertions: 404557
Failures:   0
Errors: 0

File search:00:00:05.142821
Suite construction: 00:00:00.549604
Test execution: 00:04:58.754336
Total time: 00:05:04.907839

So the release candidate is good for all recent versions of macOS.

+1
:)

On Raspberry Pi (both ARMv7 32 bit and ARMv8 64-bit) we can build and test 
without error when running locally but we occasionally run out of memory (we 
only have 1GB on Raspberry Pi), so I will install a headless version that uses 
less memory for Jenkins. I general I would say that 1 GB of memory is too 
little on any platform right now, I have allocated 2 GB to all agents (all 
agents have a GUI of some kind). Just as a background info.

I will try to install NetBSD and OpenBSD on a physical machine to find out why 
they test with more problems than FreeBSD, that works fine except for some 
timing issues related to the VM. I am backing up everything on the retired 
windows machine so if you had something there let me know and I will save it.

The Release Candidate folder is now visible and have 37 artefacts (installers) 
available for download. It was recommended to put a Readme.txt in that folder, 
I can upload it if someone provides the text.


Great, thank you very much!

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel