octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #51329] nth_element / median function fail wit


From: anonymous
Subject: [Octave-bug-tracker] [bug #51329] nth_element / median function fail with disable_range(true) (or with --traditional)
Date: Thu, 29 Jun 2017 12:28:53 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Follow-up Comment #26, bug #51329 (project octave):

I had a misunderstanding of what --traditional actually did. The only case
this could cause an issue with is some odd use of eval. (Which might actually
exist given what I've seen in Matlab)

Two options enabled with --traditional are vital for us. 

This option:
Fsave_default_options (octave_value ("-mat-binary"));

Prevents us from have to edit save options in Matlab libraries and existing to
accomplish that. Or having a runtime switch at the top of each script like
this:

if exists('OCTAVE_VERSION', builtin)
  save_default_options ("-mat-binary")
end

This option:
confirm_recursive_rmdir
Has bearing on a lot of our tools built in Matlab/Octave code that would have
to be set with a runtime flag as well.

So for now, the traditional option is vital to our, and I expect, others
scripts. Instead of removing --traditional we could remove the range option
from --traditional as a start, that would fix this bug and likely not affect
people who are trying to run Matlab in Octave.

I think in our scripts we may try to ease out of --traditional in the
meantime.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51329>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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