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

[John W. Eaton]

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

I'm attaching a fix for this problem, including a change that fixes the error
reporting to use the correct line from the file rather than the current input
line where the lexer is currently reading.  I can split those two things into
separate patches, but I don't see a good way to fix the bug without changing a
public interface.  Although the patch adds some methods to the symbol table
classes, those could be eliminated.  The real problem is that
base_parser::finish_function may already return 0, but that doesn't
necessarily indicate an error.  So I added a status flag as an argument.  It's
still not as neat and clean as I would like, but it appears to work.


(file #39429)
    _______________________________________________________

Additional Item Attachment:

File name: diffs.txt                      Size:6 KB


    _______________________________________________________

Reply to this item at:

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

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