[Octave-bug-tracker] [bug #54801] Errors in subfunctions do not create a valid link to the source code in the command window

[Lars Kindermann]

Follow-up Comment #6, bug #54801 (project octave):

right, my example was a script file called "bar.m"  
Maybe more intuitive, this bar.m shows a similar effect:


function bar
 function foo
  xyz 
 end
 foo
end


except that the message is a bit different now: 


>> bar

error: 'xyz' undefined near line 3 column 3
error: called from
    bar>foo at line 3 column 3
    bar at line 5 column 2


Now foo is recognized to sit within bar, but clicking the line


    bar>foo at line 3 column 3


will open an "Ocatve Error" message box, now stating


Can not find function bar>foo


Obviously scripts and functions are handled differently but neither correctly.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54801>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/