CODEWITHSUNDEEP
javascript
Kat
Kat

Reputation: 4695

Use of future reserved keywords in older standards

According to the MDN, there's a number of words that were reserved for future use only in older versions of the standard (specifically ECMAScript 1 till 3).

If I understand correctly, this means that they are no longer reserved. And indeed, they do not appear in the list of reserved words for ECMAScript 5.1 (there was no EMCAScript 4).

So is there any reason not to use one of these previously reserved words in a modern JavaScript application? For example, I've found that words like char, byte, or int can be useful identifiers.

Upvotes: 0

Views: 41

Answers (1)

Bergi
Bergi

Reputation: 664620

So is there any reason not to use one of these previously reserved words in a modern JavaScript application?

Not really. Except that for some reason you had to support one the old - really old - browsers which use ES3.

Upvotes: 1

Related Questions