Page 1 of 1

Future Reserved Words

Posted: Wed Feb 24, 2010 5:31 pm
by pablo_cretino
There are some "Future Reserved Words" on the editor that I don't think that they exist neither on the ES3 or the ES5. I saw some of them on the ES4 proposal, but since it didn't get approved, it would be nice to remove them from the "Future Reserved Words" list, such as "get", "set", "each" and "namespace".

I don't really know about others, but it would be nice to also know the list of words that are considered as "Future Reserved Words" by the Spket editor.

Posted: Thu Feb 25, 2010 9:15 am
by eric_suen
Some of these actually are "Contextually Reserved Words", "each" and "namespace" are Contextually Reserved Words in E4X, and "get", 'set" are from mozilla javascript syntax.

Posted: Thu Feb 25, 2010 12:41 pm
by pablo_cretino
Well, in that case it would be nice to be able to separate (or even disable) those "Contextually Reserved Words" in a different category since they aren't really part of the ECMA-262 (but part of the ECMA-357).

And about "get" and "set", I saw them on the Javascript 2 draft, but they are nowhere to be found in any of the mozilla's javascript 1.X specification. And since they aren't even on the ES5's "Future Reserved Words" list, I think it would be safe to remove them from the SPKET's "Future Reserved Words".

What you guys think?

Posted: Thu Feb 25, 2010 1:29 pm
by eric_suen ... nd_Setters

Contextually Reserved Words can be solved by semantic highlighting, Spket IDE will support semantic highlighting.

Posted: Thu Feb 25, 2010 1:41 pm
by pablo_cretino
Cool! Can't wait 'till its done =]

Good job then