GNU Octave - Bugs: bug #62283, max (a, b) produces unintuitive...
bug #62283: max (a, b) produces unintuitive results when mixing integers and floating point values
Follow 10 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-06-28 | arungiridhar | Status | Ready For Test | ![]() |
Fixed |
Open/Closed | Open | ![]() |
Closed | ||
2022-06-04 | arungiridhar | Status | Confirmed | ![]() |
Ready For Test |
2022-04-11 | arungiridhar | Attached File | - | ![]() |
Added doc.patch, #53076 |
2022-04-10 | rik5 | Category | Documentation | ![]() |
Octave Function |
Item Group | Unexpected Error or Warning | ![]() |
Documentation | ||
Status | None | ![]() |
Confirmed | ||
Release | 6.4.0 | ![]() |
dev | ||
Operating System | Microsoft Windows | ![]() |
Any | ||
Summary | max (a, b) gives neither a nor b but a random third value | ![]() |
max (a, b) produces unintuitive results when mixing integers and floating point values |
Powered by Savane 3.14-573e.
Corresponding source code