[Octave-bug-tracker] [bug #62283] max (a, b) produces unintuitive results when mixing integers and floating point values

[A.R. Burgers]

Follow-up Comment #3, bug #62283 (project octave):

This issue can manifest itself in many ways.
Maybe an idea to issue a warning with ID (that can be disabled/enabled) in an
earlier stage:


warning: double (%g) truncated to (%d) on conversion to type %s


But I guess that opens a box of pandora.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62283>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/