octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62283] max (a, b) gives neither a nor b but a


From: anonymous
Subject: [Octave-bug-tracker] [bug #62283] max (a, b) gives neither a nor b but a random third value
Date: Sun, 10 Apr 2022 14:53:20 -0400 (EDT)

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

                 Summary: max (a, b) gives neither a nor b but a random third
value
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 10 Apr 2022 06:53:18 PM UTC
                Category: Documentation
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.4.0
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

 a = int8 (100);  b = 200;  max (a, b)

Expected 200, but got 127.

Weird rule for integers. Better to say "cannot call max for mixing int8 and
double".

Was not documented in max so this bug report to ask to document this weird
result.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]