[Octave-bug-tracker] [bug #60882] error parsing command syntax

[John W. Eaton]

Follow-up Comment #11, bug #60882 (project octave):

I pushed the following change for now:

http://hg.savannah.gnu.org/hgweb/octave/rev/0b01806bb663

As noted in one of the comments I added, it might be possible to store the
(expected) variable status of symbols in the symbol_scope object instead of in
a separate list of sets.

Also, as noted in the discussion here: 
https://octave.discourse.group/t/need-help-understanding-matlab-behavior/1313/12,
we might be able to do a better job of parsing command-style function call
syntax and detecting variables later used as commands if we always consider an
identifier at the beginning of a statement as a possible command when parsing
a function and parse it that way regardless of the status of any symbols that
appear to be variables. Then, after the file is completely parsed and
subfunctions and nested function scopes have been sorted out, walk the parse
trees of the functions defined in the file and detect any command-style
function calls that are using a symbol name that has previously appeared to be
used as a variable. If I have some free time I’ll take a look at doing that.

    _______________________________________________________

Reply to this item at:

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

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