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

[John W. Eaton]

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

                 Summary: eval (code) when code could be parsed as a command
                 Project: GNU Octave
            Submitted by: jwe
            Submitted on: Wed 30 Jan 2019 08:45:36 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: jwe
         Originator Name: jwe
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

When the eval function parses an expression, it must decide when to parse an
expression like


foo -bar   ## (1)


as a command or subtraction expression.  Octave doesn't behave the same as
Matlab now.  For example, any time eval is called with an output argument, the
expression is not allowed to be a command.  This corresponds to not parsing
the "foo -bar" part of expressions like


val = foo -bar


as commands even though


foo -bar


by itself is parsed as a command.

Similarly, if foo is known to be a variable, then the expression (1) above
will not be parsed as a command.

See also bug #38576 and the following discussion on the maintainers mailing
list:
http://lists.gnu.org/archive/html/octave-maintainers/2019-01/msg00303.html

I'll update the file test/bug-38576.tst once I have a bug report number.




    _______________________________________________________

Reply to this item at:

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

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