Comments on: Don’t use future reserved words as identifiers in JavaScript http://www.xaprb.com/blog/2005/12/23/future-reserved-words/ Stay curious! Thu, 02 May 2013 12:36:53 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Xaprb http://www.xaprb.com/blog/2005/12/23/future-reserved-words/#comment-15938 Xaprb Sat, 07 Mar 2009 18:28:04 +0000 http://www.xaprb.com/blog/?p=71#comment-15938 I didn’t know that!

]]>
By: Tim McCormack http://www.xaprb.com/blog/2005/12/23/future-reserved-words/#comment-15935 Tim McCormack Sat, 07 Mar 2009 18:08:00 +0000 http://www.xaprb.com/blog/?p=71#comment-15935 Don’t forget that Netscape’s Javascript has Java compatibility baked in, so you can refer directly to things like java.util.Vector in your scripting. The implication is that all Java reserved words and top-level package names (java, javax, and sun, and probably com, org, net, and edu as well) are reserved in Netscape’s version of ECMAscript.

]]>
By: Rock and Roll http://www.xaprb.com/blog/2005/12/23/future-reserved-words/#comment-11780 Rock and Roll Thu, 21 Jun 2007 10:27:27 +0000 http://www.xaprb.com/blog/?p=71#comment-11780 That’s common practice.

]]>
By: Bill Gates http://www.xaprb.com/blog/2005/12/23/future-reserved-words/#comment-82 Bill Gates Fri, 03 Feb 2006 00:03:19 +0000 http://www.xaprb.com/blog/?p=71#comment-82 Confirmed, co-incidentally, with Safari 1.3. Firefox 1.5 had no problem, though.

]]>