1,207
edits
Online Developer Meeting (2025-08-26): Difference between revisions
Jump to navigation
Jump to search
m
Strikethrough items done
(Create page) |
m (Strikethrough items done) |
||
| Line 8: | Line 8: | ||
* 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''' | * 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? '''Done by Markus''' | * Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now? <s>'''Done by Markus'''</s> | ||
* 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''' | * 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) <s>'''Arun has fix implemented for bug #67339. Thus, pressing need to resolve other problems with `mod` is gone'''</s> | ||
* 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.''' | * 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. '''Expand documentation on how to use NA properly. It may not be preserved in numerical context''' | * 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. <s>'''Expand documentation on how to use NA properly. It may not be preserved in numerical context'''</s> | ||
* Availability of hg.savannah.gnu.org for buildbots. '''jwe will point buildbots at hg.octave.org instead''' | * Availability of hg.savannah.gnu.org for buildbots. <s>'''jwe will point buildbots at hg.octave.org instead'''</s> | ||
== See also == | == See also == | ||