[Octave-bug-tracker] [bug #50014] Octave segmentation violation when duplicate nested functions exist

[Rik]

Follow-up Comment #3, bug #50014 (project octave):

Also of interest, the parser accepts duplicate subfunction names, but uses the
first definition of the function.  It seems like it would be helpful if the
parser were to issue a warning or an error on encountering the second
duplicate subfunction.

Test case in the file testbug2.m:


function x = testbug2()

  x = 1;

endfunction

function y = testbug2()

  y = 2;

endfunction


Then execute


octave:1> testbug2
ans =  1




    _______________________________________________________

Reply to this item at:

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

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