|
From: | Nicholas Jankowski |
Subject: | [Octave-bug-tracker] [bug #51329] Median fails due to nth_element in --traditional |
Date: | Wed, 28 Jun 2017 15:57:17 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #9, bug #51329 (project octave): yes, right. Since the only affect of disable_range is to change median's range input to nth_element into a vector, and it only seems to be triggering a type-check failure, allowing a vector input should fix it. The only other issue I could imagine is that a range is inherently sorted, so the code might be relying on that assumption. It may be necessary to do a sort check of some kind for input-type=vector. (suggested by the fact that the error is triggered by mode = UNSORTED) _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?51329> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |