why jslint suggest we declare local (var) variables at the top of function?

Jang · Jun 15, 2007

In jslint's doc it says, "JSLint does not expect that a var will be
defined in a block. This is because JavaScript blocks do not have
block scope. This can have unexpected consequences. Define all
variables at the top of the function."

What are some of those unexpected consequences?

Lee · Jun 15, 2007

Jang said:

In jslint's doc it says, "JSLint does not expect that a var will be
defined in a block. This is because JavaScript blocks do not have
block scope. This can have unexpected consequences. Define all
variables at the top of the function."

What are some of those unexpected consequences?

People expecting block scope have been surprised to find
that code like the following loops infinitely:

<html>
<body>
<script type="text/javascript">

function demo() {
for(var i=0;i<10;i++) {
document.write(i+":");
for(var i=0;i<5;i++) {
document.write(" "+i);
}
document.write("<br>");
}
}
demo();
</script>
</body>
</html>

--

$var = do { ... }?	26	Mar 2, 2012
using getattr/setattr for local variables in a member function	5	Nov 21, 2013
Default scope of variables	55	Jul 4, 2013
How to use PDF-lib and how to center each line of texts on the page?	1	Aug 16, 2023
Function Declaration as anti-pattern?	8	Jan 27, 2012
local var naming style	25	Oct 7, 2007
initialization order of function local static variables	9	Mar 9, 2010
Where Should Variables be Declared?	2	Sep 16, 2009

why jslint suggest we declare local (var) variables at the top of function?

Jang

Lee

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads