Thanks for taking the time on this Rony. I have added my thoughts to
yours below.
On 3/6/2025 6:25 AM, Rony G. Flatscher wrote:
Terry, thank you for resending this!
In the meantime I took the time to go through all of the listed items
(quite time consuming).
Here explicitly listed with my findings and the requests for takers,
so please read through these items quickly and if you think you could
lend your hand then please say so.
On 19.02.2025 19:41, taf wrote:
from Gil:
"I have summarized the open 5.0.0 issues twice already and a simple
search by anyone interested of this discussion group around the Q4
time frame will find the items that others have identified as needing
to be addressed before a new release is produced."
I've attached a summary of the items listed in Gil's note of
2024.12.21, 07.12 with subject line:
*/Re: [Oorexx-devel] Ad creating a release of ooRexx 5.1.0, please
give feedback/*
Checking out the original entries from your attachment which
communicates Gil's list:
* Bug tracker related (to get to the respective bug tracker page
just change the number at the end of this URL appropriately:
https://sourceforge.net/p/oorexx/bugs/1447/)
o # 1447 "Clean builds without compiler warnings", created:
2017-05-09
It seems that the code got fixed by Erich (last commit on
2021-03-07), such that the "Pending work items: code" seems to
be wrong;
@Erich: could you please double-check?
o #1624 ".Routine~newFile(rexxc-program) raises error 13.1",
created: 2019-04-17
"Pending work items: doc+test": will take on this one myself
As it seems that only tests were needed, I suggest we simply close this
item (and any others that do not involve either code changes and/or
documentation changes).
o #1625 "NewRoutine() and LoadPackageFromData() raise error 13.1
on tokenized Rexx code", created: 2019-07-16
"Pending work items: doc+test": the only pending item is
"test" (the documentation never indicated whether a program is
compiled or not). Any takers for adding the necessary tests to
"ooRexx/API/oo/"?
As it seems that only tests were needed, I suggest we simply close this
item (and any others that do not involve either code changes and/or
documentation changes).
o #1656 "Lineout fails (at 2nd call) when path case not
matched", created: 2019-10-09
"Pending work items: doc+code": this seems to be wrong as a
fix is in place and no documentation is needed.
Suggestion: correct "Pending work items" and status to "closed".
+1
o
o #1742 "Stream RECLENGTH 1 issues", created: 2021-02-05, fixed
the same day by Erich
"Pending work items: test": this could be probably done by
everyone on this list, any takers?
o #1762 "pushing very large data hangs RexxQueue", created:
2021-05-04, last update: 2021-07-07
"Pending work items: code+test": it seems that there is no fix
as of yet.
@Erich & @Rick: what do you think about this, is this still an
open bug? If not, how to fix it?
o #1763 "StreamSocket issues", created: 2021-05-11, last update:
2022-06-27
"Pending work items: code+doc+test": it seems that this got
fixed by Erich on 2021-05-12 already?
If so, anyone on this list could edit the documentation and
create a test, any takers?
o #1786 "RexxPullFromQueue() returning invalid data for a null
queue entry", created: 2021-11-05, last update: 2021-11-05
"Pending work items: test": any takers?
o #1827 "13 Sample files missing shebang", created: 2022-07-05,
last updated: 2023-07-23
"Pending work items: code+test": any takers?
o #1837 "circular requires: some public classes are not
visible", created: 2022-08-09, last update: 2022-12-20
"Pending work items: doc+test": editing documentation probably
not necessary, just the test; any takers?
o #1838 "Crash while attempting to resolve a routine in a
library package.", created: 2022-08-11, last update: 2024-11-21
No pending work items, hence already completed!
Suggestion: change status to "pending".
Change to Closed.
o
* Feature Request tracker related (to get to the respective bug
tracker page just change the number at the end of this URL
appropriately: https://sourceforge.net/p/oorexx/feature-requests/353/)
o #353 "Embedded Database", created: 2009-05-01, last update:
2012-12-21, status: accepted
"Pending work items: docs"; Mark Miesfield created "ooSQLite",
unfortunately, he has passed away back then.
Looking at the given link
<https://sourceforge.net/projects/oorexx/files/ooSQLite/>,
there are Linux and Windows versions from January 2023.
Not sure why this is listed.
Also, it would be possible to use BSF4ooRexx and use JDBC to
not only interact with SQLite but also with all databases on
all operating systems that have a JDBC interface. Ad SQLite
JDBC-driver: as SQLite is so small the JDBC driver includes
the binaries for all major operating systems (Windows, Apple,
Linux) such that only the SQLite-JDBC driver would be needed.
Suggestion: keep state as is for the planned release of 5.1.0,
discuss afterwards what to do with it.
For items like this, I'd rather see them closed and new items opened
with a new target release.
o #554 "Enhance stand alone ooDialog installer to use
components", created: 2013-10-20, last update: 2014-01-19,
status: closed!
Nothing to do!
I think this one was a typo as my list shows #544 Allow the registration
of user defined SQL functions and aggregates with a TODO of doc.
o #552 "Add the ToolBar control to ooDialog", created:
2013-09-12, last update: 2013-09-21, status: accepted,
milestone: ooDialog.4.2.3
"Pending work items: code+doc+test"; created and code support
by Mark Miesfield, not sure about state, nor why it made it to
this list of open items with regard to 5.0.0. Also not sure
about "ooDialog.4.2.3", not being a user of ooDialog.
Any comments, insights, anyone?
Suggestion: keep state as is as long as no ooDialog savvy
developer steps forward to finalize this RFE.
Again, for items like this, I'd rather see them closed and new items
opened with a new target release.
o #569 "Allow direct creation of dialog control windows.",
created: 2013-12-21, last update: 2013-12-21, status:
accepted, milestone: ooDialog.4.2.3
"Pending work items: code+doc+test"; created and code support
by Mark Miesfield, not sure about state, nor why it made it to
this list of open items with regard to 5.0.0. Also not sure
about "ooDialog.4.2.3", not being a user of ooDialog.
Any comments, insights, anyone?
Suggestion: keep state as is as long as no ooDialog savvy
developer steps forward to finalize this RFE.
Again, for items like this, I'd rather see them closed and new items
opened with a new target release.
o #576 "Add support for the 'split button'", created:
2013-12-25, last updated: 2013-12-25, status: status:
accepted, milestone: ooDialog.4.2.3
"Pending work items: code+doc+test"; created and code support
by Mark Miesfield who commented: "Partially implemented, need
to finish implementation, test, and doc.". Not sure why it
made it to this list of open items with regard to 5.0.0. Also
not sure about "ooDialog.4.2.3", not being a user of ooDialog.
Any comments, insights, anyone?
Suggestion: keep state as is as long as no ooDialog savvy
developer steps forward to finalize this RFE.
Again, for items like this, I'd rather see them closed and new items
opened with a new target release.
o #571 "Support extended window styles for dialog and dialog
control windows", created: 2013-12-24, last updated:
20213-12-24, status: open, no work done.
Not sure why it made it to this list of open items with regard
to 5.0.0. Also not sure about "ooDialog.4.2.3", not being a
user of ooDialog.
Any comments, insights, anyone?
Suggestion: keep state as is as long as no ooDialog savvy
developer steps forward to finalize this RFE.
Again, for items like this, I'd rather see them closed and new items
opened with a new target release.
o #581 "Add item data capability to combo box", created:
2014-01-30, last updated: 2014-01-30, status: accepted, no
work done.
Not sure why it made it to this list of open items with regard
to 5.0.0. Also not sure about "ooDialog.4.2.3", not being a
user of ooDialog.
Any comments, insights, anyone?
Suggestion: keep state as is as long as no ooDialog savvy
developer steps forward to finalize this RFE.
o #603 "Add a GUARD ON/OFF capability to the MethodContext
APIs.", created: 2014-07-04, last updated: 2018-12-07, status:
accepted
"Pending work items: test";
After checking the sources, documentation and the tests, it is
clear that the status is wrong! Everything got implemented,
documented and tested!
Suggestion: change status to "closed"
+1
o 754 "'rexxc' binary (compiled/tokenized) data: please encode
as plain text (7-Bit-ASCII)", created: 2019-04-07, last
updated: 2020-03-08, status: accepted
"Pending work items: test";
This has been implemented and documented, the test is missing.
Will take on this pending work item myself.
As it seems that only tests were needed, I suggest we simply close this
item (and any others that do not involve either code changes and/or
documentation changes).
o #803 "extensions to complex.cls", created: 2022-06-02, last
update: 2022-06-03, status: accepted
"Pending work items: test";
This has been implemented, the test is missing, also
"samples\usecomp.rex" should demonstrate the use of the new
methods "**" (power) and "sqrt" (square root).
@Walter: could you add the new methods to "samples\usecomp.rex"?
And maybe even create tests for the testing framework to
"test/trunk/ooRexx/samples/complex.testGroup"?
Request for feedback and help!
---rony
P.S.: In case you would be interested to help, but have never used the
ooRexx testing framework then please ask for pointers. Here a pointer:
<https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/>
(here the very first introduction to the framework:
<https://www.rexxla.org/presentations/2006/ronyf2.pdf> and
<https://wi.wu.ac.at/rgf/rexx/orx17/2006_orx17_ooRexxUnit-article.pdf>).
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
