1,207
edits
Online Developer Meeting (2025-07-22): Difference between revisions
Jump to navigation
Jump to search
m
→Today's topics
m (Add new topics) |
m (→Today's topics) |
||
| Line 7: | Line 7: | ||
* 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? | ||
* Should we discontinue NA? Implementation relies on bit signature in value that represents NaN. Not all CPUs seem to respect this. | * Should we discontinue NA? Implementation relies on bit signature in value that represents NaN. Not all CPUs seem to respect this. | ||
* 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 () | * 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 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. 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? | ||