Re: Obsolete parser tokens?

[Rik]

On 01/30/2012 01:57 PM, John W. Eaton wrote:
> On 28-Jan-2012, Rik wrote:
>
> | It seems like the keywords 'static', 'get', and 'set' could possibly be
> | removed from the parser.  According to Mercurial, it appears 'static' was
> | obsoleted by 'persistent' on 11/12/2002.  9 years would appear to be enough
> | time to get rid of any references in outstanding code.    'get' and 'set'
> | seem not to be used as keywords.  Rather, the set() and get() functions in
> | src/graphics.cc are what Octave uses when it encounters these words.
>
> I would not object to removing it "static" as a reserved keyword, but
> I checked, and there are some .m files in Octave Forge that are still
> using it.  So before removing it completely, we should probably warn
> that it is deprecated for a few releases first.
Could you do this?  I know how to deprecate a function, but deprecating a
keyword is different and I have no experience with that part of the code.
> Although set and get are normally function names, they are also
> recognized specially for some kind of classdef syntax.  They are not
> keywords in Matlab though, so we could probably also fix Octave to
> handle this syntax without requiring actual reserved keywords.
>
That is what I was thinking.  I checked Matlab's keywords and they don't
have 'get' or 'set' so I think we could do without.

--Rik