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

From Octave
Jump to navigation Jump to search
m (Undo revision 15462 by Rik (talk))
Tag: Undo
 
(8 intermediate revisions by the same user not shown)
Line 4: Line 4:
== Today's topics ==
== Today's topics ==


* Replace the abundant files in <code>liboctave/operators/</code> with modern C++ templates?  (Seems like use of modern C++ templates might work)
* Replace the abundant files in <code>liboctave/operators/</code> with modern C++ templates?  (Seems like use of modern C++ templates might work) '''Start a Discourse thread on what code pattern to use'''
* Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now?
* Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now? '''Done by Markus'''
* 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)
* 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) '''Arun has fix implemented for bug #67339.  Thus, pressing need to resolve other problems with `mod` is gone'''
* 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? '''jwe will look at changing GUI code to have save operation emit a signal when file save has finished.  Only then will GUI advance to running the file.'''
* 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.
* 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. '''Expand documentation on how to use NA properly.  It may not be preserved in numerical context'''
* Availability of hg.savannah.gnu.org for buildbots.
* Availability of hg.savannah.gnu.org for buildbots. '''jwe will point buildbots at hg.octave.org instead'''


== Previous topics ==
== Previous topics ==

Latest revision as of 08:41, 1 August 2025

Today's topics

  • Replace the abundant files in liboctave/operators/ with modern C++ templates? (Seems like use of modern C++ templates might work) Start a Discourse thread on what code pattern to use
  • Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now? Done by Markus
  • 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) Arun has fix implemented for bug #67339. Thus, pressing need to resolve other problems with `mod` is gone
  • 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? jwe will look at changing GUI code to have save operation emit a signal when file save has finished. Only then will GUI advance to running the file.
  • Should we discontinue NA? Implementation relies on bit signature in value that represents NaN. Not all CPUs seem to respect this. Expand documentation on how to use NA properly. It may not be preserved in numerical context
  • Availability of hg.savannah.gnu.org for buildbots. jwe will point buildbots at hg.octave.org instead

Previous topics

  • 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.)

See also

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2025-07-22)&oldid=15464"