[Octave-bug-tracker] [bug #29476] Parser incompatibility for keywords against Matlab implementation, infinite loop

[John W. Eaton]

Follow-up Comment #13, bug #29476 (project octave):

I don't really want to invent new syntax for this feature.  I would just like
to think about whether there is a way that we can make the compatibility
freaks happy without doing too much damage (i.e., I don't want to eliminate
the extended keywords completely).

There is no problem with parsing structure elements now.  You should already
be able to write x.foo = 42, for example.

The only case I can think of where you might need to access a symbol that has
the same name as one of the extra Octave keywords is if you need to call a
function or a global variable that is defined with the keyword name.  For
functions, we already have feval.  I guess we would need some way to get a
(global) variable value via a function.  That should be simple enough to do.

Or, maybe it is not needed at all, since if you started Octave with
--traditional to allow this feature to work in .m files at all, then maybe you
should not be able to use the extended set of Octave keywords at the command
line either?  And if you need to write a function that must access global
variables or functions that have keyword names, then you can just write it
using the --traditional mode.


    _______________________________________________________

Reply to this item at:

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

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