[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #65000] dec2hex problem
From: |
Charles Praplan |
Subject: |
[Octave-bug-tracker] [bug #65000] dec2hex problem |
Date: |
Fri, 8 Dec 2023 10:01:32 -0500 (EST) |
URL:
<https://savannah.gnu.org/bugs/?65000>
Summary: dec2hex problem
Group: GNU Octave
Submitter: charprap
Submitted: Fri 08 Dec 2023 03:01:30 PM UTC
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Charles Praplan
Originator Email:
Open/Closed: Open
Release: 8.4.0
Discussion Lock: Any
Operating System: Microsoft Windows
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fri 08 Dec 2023 03:01:30 PM UTC By: Charles Praplan <charprap>
dec2hex function produces bad formatted output for vector inputs, if all
output values have only one digit. This leads to wrong interpretation of the
result as illustrated in the following example:
>> dec2hex([5, 9])
ans = 59
But in the next examples, the behavior is correct:
>> dec2hex([5, 9],2)
ans =
05
09
>> dec2hex([16, 9])
ans =
10
09
The problem is not new. It was already present in version 7.3.0 but not in
version 6.4.0.
The problem is the same for line or column vectors.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65000>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #65000] dec2hex problem,
Charles Praplan <=