[Octave-bug-tracker] [bug #58323] '...' continuation marker causes parse error when executed with "run selection" in GUI editor

[Markus Mützel]

Follow-up Comment #20, bug #58323 (project octave):

Thanks for the changes. Imho this looks better now.

Thinking about it again, the way Matlab is doing it ("history" before the
rest) makes actually a lot more sense to me.
For a reference assume that you are entering the following at the command
prompt:

>> a = sum(one(3,1)
; b=5;
error: parse error:

  syntax error

>>> ; b=5;
    ^


The command in the second line didn't execute. Yet it appears in the command
history (which is a good thing imho). So it wouldn't be anything out of the
ordinary if commands that never executed appear in the command history.

Then assume that you are F9'ing the following lines:

a = 5
b = 1
a
keyboard
3
b


Maybe the code is more complicated and you added the keyboard statement to
manually do a bunch of tests and calculations before you eventually continue
execution with "dbcont".
I haven't tried the patch yet. But from what you were writing, I guess that
the F9'ed code would be added to the command history after that session.
In this case, the code that would appear last in the command history is *not*
the code that was sent to the interpreter last.
Imho, Matlab got it the right way round.

    _______________________________________________________

Reply to this item at:

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

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