[Octave-bug-tracker] [bug #47796] GUI allows breakpoints to be set on empty line at EOF

[Lachlan Andrew]

Follow-up Comment #1, bug #47796 (project octave):

Is that a bug or a feature?

A breakpoint stops *before* the command is executed.  This breakpoint on the
blank line causes a breakpoint to occur *after* the last command of the script
is executed, but before returning to the caller.  That would be impossible if
breakpoints could only be placed on non-empty lines.

Regarding dbstatus, note that the file and octave are resynchronised when the
file is saved.  Matlab turns the breakpoint symbol grey when the file has been
edited.  We already have a visual indication that the file has been edited
(the star in the tab), and so the alert user can know that the position of the
breakpoint can't be trusted.

    _______________________________________________________

Reply to this item at:

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

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