[JAVASCRIPT] Javascript Serialize

[jscheuer1]

That tells you what type of data (variable name: boolean, integer, string, etc.) in the variable, not the type of keyword. Well, as far as I know.

That's what I said but, why not? I mean why wasn't that included in its scope? Like:

alert(typeof try);

should return 'undefined' in browsers before try was instituted and 'reserved' or 'keyword' in browsers where try has been implemented. That way no reserving would ever be needed until a use for something was devised and implemented.

I realize that this would open up legacy code to errors in modern browsers but, that is already the case. I just think reserving words is a sort of anal compulsion on the part of the language developers with no thought as to how it will effect code written both before and after the reserved word finds a use.

[Twey]

I think you just answered your own question.

Aye, I know it's possible, but the way you put it made it sound as if it would be easier if older browsers didn't die on the keyword, whereas in fact the difference would be negligable.

They should have just left 'try' out of consideration entirely so that it could be tested for as an available method without causing older browsers to barf.

The first piece of my code is what would be necessary to check for final if older browsers reserved it; the other is what's necessary as is. As you can see, both are pretty much equally ugly.

With regards to using typeof for keywords: it may be possible, but since keywords are part of the language proper, they're not objects; it would be very difficult to tell how the developer intended to use the keyword in a given situation.