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

[John W. Eaton]

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

It's a feature that you can set a breakpoint at or step to the end of a
function or script after all executable statements have been evaluated.  That
way you can examine all variables that have been set.  I guess you can think
of it as setting a breakpoint just before the implicit "return" statement is
evaluated.  I think Matlab also behaves this way.

I see 6 returned from dbstop instead of 7 and if I try dbstop FILE 6, it
returns 0.  But maybe you have one more blank line in the file than I do?


    _______________________________________________________

Reply to this item at:

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

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