[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55072] Incorrect printf result
From: |
Kai Torben Ohlhus |
Subject: |
[Octave-bug-tracker] [bug #55072] Incorrect printf result |
Date: |
Thu, 22 Nov 2018 04:21:27 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 |
Update of bug #55072 (project octave):
Severity: 3 - Normal => 1 - Wish
Priority: 5 - Normal => 3 - Low
Item Group: Incorrect Result => Matlab Compatibility
Status: None => Invalid
Open/Closed: Open => Closed
Operating System: Microsoft Windows => Any
_______________________________________________________
Follow-up Comment #1:
In your case the result might seem unexpected, but you provided an signed
instead of an unsigned integer.
The given result is compatible with Matlab R2018b, you violate the range of
the data type (by the negative value). You can find more information the
manual: https://octave.org/doc/v4.4.1/Table-of-Output-Conversions.html
‘%x’, ‘%X’
Print an integer as an unsigned hexadecimal number. ‘%x’ uses lowercase
letters and ‘%X’ uses uppercase. See Integer Conversions, for details.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55072>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, анонимный, 2018/11/22
- [Octave-bug-tracker] [bug #55072] Incorrect printf result,
Kai Torben Ohlhus <=
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, Kai Torben Ohlhus, 2018/11/22
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, анонимный, 2018/11/22
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, Kai Torben Ohlhus, 2018/11/22
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, Michael Godfrey, 2018/11/22
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, Kai Torben Ohlhus, 2018/11/23
- [Octave-bug-tracker] [bug #55072] Incorrect printf result, Michael Godfrey, 2018/11/23