[Octave-bug-tracker] [bug #55610] eval (code) when code could be parsed as a command

[John W. Eaton]

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

Oops, after taking another look at the test results, I think things are
simpler than I initially thought.

If eval is called with nargout == 0, then the expression may be parsed as a
command.  Otherwise, it is never parsed as a command.

My interpretation of what happens when foo is a variable in the examples in
the original submission was incorrect.  Instead, if foo is a variable and we
are parsing


eval ("foo -bar")


then it is an error because foo is known to be a variable but syntax says that
this looks like a command.  Octave does not currently appear to behave
correctly even outside of eval expressions.

There are still compatibility issues in Octave and I'm updating the tests but
I think it should be more straightforward to fix.

    _______________________________________________________

Reply to this item at:

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

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