[Top][All Lists]

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

[Octave-bug-tracker] [bug #57528] imread always fails when Octave was st

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #57528] imread always fails when Octave was started with the "--traditional" option
Date: Fri, 3 Jan 2020 17:23:32 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

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

The relevant option is "disable_range (true)" when running Octave with
--traditional. With this option set to true, a range expression like 1:10
expands to a full matrix. But the imread function internally seems to be
depending on a range object being passed down into the lower layers, see the
function get_region_range in libinterp/corefcn/__magick_read__.cc.


Reply to this item at:


  Message sent via Savannah

reply via email to

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