[Octave-bug-tracker] [bug #38691] optim package conflicting with octave's optimization

[Mike Miller]

Update of bug #38691 (project octave):

                  Status:               Need Info => Confirmed              

    _______________________________________________________

Follow-up Comment #3:

I see now. Here is the stack at the time of the error (setting debug_on_error
followed by dbstack):


stopped in:

  -->              print_usage at line 88
[/opt/gnu/octave/share/octave/3.7.2+/m/help/print_usage.m]
                      optimget at line 32
[/opt/gnu/octave/share/octave/3.7.2+/m/optimization/optimget.m]
      fminsearch>parse_options at line 126
[/opt/gnu/octave/share/octave/3.7.2+/m/optimization/fminsearch.m]
             fminsearch>nmsmax at line 159
[/opt/gnu/octave/share/octave/3.7.2+/m/optimization/fminsearch.m]
                         fmins at line 77
[/home/mike/octave/optim-1.2.2/fmins.m]
                    fminsearch at line 33
[/home/mike/octave/optim-1.2.2/fminsearch.m]
debug> which nmsmax
'nmsmax' is a function from the file /home/mike/octave/optim-1.2.2/nmsmax.m


So the nmsmax private function in Octave's fminsearch.m is taking precedence
over the public nmsmax in the optim package, even though that copy of
fminsearch was not called.

    _______________________________________________________

Reply to this item at:

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

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