|
From: | Hartmut |
Subject: | [Octave-bug-tracker] [bug #61788] arrays of type int16 contain wrong numbers |
Date: | Fri, 14 Jan 2022 18:24:30 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0 |
Follow-up Comment #14, bug #61788 (project octave): I have observed another change in Octave 7.0.90, that is connected to arrays of integers: n = uint8(2) class(1:n) In Octave 6.4.0 this gave a class of "double". But now in Octave 7.0.90 this gives a class of "uint8". But (Online-)Matlab also gives "uint8" in this case, so maybe this is just an improvement in Octave 7.0.90? How will this behave in the future? I ask because I realised that the function regionprops.m in the image package relies on the old (and not Matlab compatible) Octave behavior (and so behaves wrongly at the moment with Octave 7.0.90). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61788> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |