Online Developer Meeting (2025-07-22): Difference between revisions

Revision as of 13:54, 22 July 2025

Replace the abundant files in liboctave/operators/ with modern C++ templates? (Seems like use of modern C++ templates might work)
Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now?
How to proceed with updating mod/rem. Current implementation gives nonsensical results for large values (bug #45481) and incorrect results for values > 2/3 flintmax () (bug #67339). Results are also not exactly Matlab compatible for various corner cases (I can't find the exact threshold they are using to determine when something is within round-off error of 0)
The F5 key (save and run code) in GUI is broken in Windows because of the operating system's poor timestamping (bug #67340). This issue has come up repeatedly. Can we resolve it, even with a hack, so that we don't get more complaints and bug reports about it?
Should we discontinue NA? Implementation relies on bit signature in value that represents NaN. Not all CPUs seem to respect this.
Availability of hg.savannah.gnu.org for buildbots.

Reorganization of liboctave (place GNU Readline in libinterp?) Rik will investigate how difficult this is
Capitalization of file names? Why is it Cell.h, not cell.h? Other examples, Quad.h, DASPK.h. (Probably too hard because of case-insensitive file systems.)

@@ Line 7: / Line 7: @@
 * Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now?
 * How to proceed with updating <code>mod</code>/<code>rem</code>.  Current implementation gives nonsensical results for large values ([https://savannah.gnu.org/bugs/index.php?45481 bug #45481]) and incorrect results for <code>values > 2/3 flintmax ()</code> ([https://savannah.gnu.org/bugs/index.php?67339 bug #67339]).  Results are also not ''exactly'' Matlab compatible for various corner cases (I can't find the exact threshold they are using to determine when something is within round-off error of 0)
-* The F5 key (save and run code) in GUI is broken in Windows because of the operating system's poor timestamping.  This issue has come up repeatedly.  Can we resolve it, even with a hack, so that we don't get more complaints and bug reports about it?
+* The F5 key (save and run code) in GUI is broken in Windows because of the operating system's poor timestamping ([https://savannah.gnu.org/bugs/index.php?67340 bug #67340]).  This issue has come up repeatedly.  Can we resolve it, even with a hack, so that we don't get more complaints and bug reports about it?
 * Should we discontinue <code>NA</code>?  Implementation relies on bit signature in value that represents <code>NaN</code>.  Not all CPUs seem to respect this.
 * Availability of hg.savannah.gnu.org for buildbots.