Best to be clear and consistent in your code. I always use the first form. the second is needlessly verbose and only useful if you are creating a global inside of another scope (why?), and the third is "sloppy"
On Jan 7, 2:46 am, Mathias Bynens <math...@qiwi.be> wrote: > You’re in the global scope, and you want to create a new global var. > There are different options. What is the difference between them? > > 1) This will work because the current scope happens to be the global > scope: > > var foo = 42; > > Obviously, this would fail to create the var in the global scope when > called from inside another scope. > > 2) Another option is to use: > > window.foo = 42; > > This will work regardless of the scope it’s called from. > > 3) When called from the global scope, you can omit var and just go > like this: > > foo = 42; > > Let’s assume you’re working in the global scope already and you want > to create a new global variable. What do you guys recommend? Should > the `var` keyword be used (first example) even though it’s not > necessary in this case? Are there any other implications I should be > aware of? What is considered to be the best practice here? -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/jsmentors@jsmentors.com/ To search via a non-Google archive, visit here: http://www.mail-archive.com/jsmentors@googlegroups.com/ To unsubscribe from this group, send email to jsmentors+unsubscr...@googlegroups.com
