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

[Mike Miller]

Follow-up Comment #4, bug #38691 (project octave):

This took a while but I have a standalone test that demonstrates the problem
in the function resolution being seen here. As a workaround, "clear -f" makes
fminsearch work again after the optim package has been added to the path.

I don't have an idea where occurs yet, but I've started reading into the
symbol table classes. Of course input from someone else more familiar with the
symbol table would be welcome.

Example follows:


$ ls -R dir*
dir1:
func1.m

dir2:
func1.m  func2.m  func3.m
$ octave -qf
octave:1> addpath ("dir1")
octave:2> func1 (0)
dir1/func1 (0)
dir1/func2 (0)
dir1/func3 (0)
ans = 0
octave:3> addpath ("dir2")
octave:4> func1 (0)
dir2/func1 (0)
dir2/func2 (0)
dir1/func3 (0)
ans = 0
octave:5> clear -f
octave:6> func1 (0)
dir2/func1 (0)
dir2/func2 (0)
dir2/func3 (0)
ans =  3.1416


Attached zip contains the above files as well as a script that runs the
commands I've shown in the session above.

(file #27992)
    _______________________________________________________

Additional Item Attachment:

File name: subfuncpaths.zip               Size:1 KB


    _______________________________________________________

Reply to this item at:

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

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