Comments on: JavaScript and the Semicolon http://trevorpowell.com/2008/03/20/javascript-and-the-semicolon/ Trevor Powell. An online experiment in web standards, internationalization, and localization. Thu, 20 Nov 2008 21:19:14 +0000 http://wordpress.org/?v=2.6.2 By: Trevor http://trevorpowell.com/2008/03/20/javascript-and-the-semicolon/#comment-258 Trevor Fri, 21 Mar 2008 00:07:59 +0000 http://trevorpowell.com/2008/03/20/javascript-and-the-semicolon/#comment-258 Rewrite the function expression in there as a statement and it works! <pre><code>function fn(){console.log("hi");}a=2;</code></pre> Rewrite the function expression in there as a statement and it works!

function fn(){console.log("hi");}a=2;
]]> By: joy http://trevorpowell.com/2008/03/20/javascript-and-the-semicolon/#comment-257 joy Thu, 20 Mar 2008 22:05:38 +0000 http://trevorpowell.com/2008/03/20/javascript-and-the-semicolon/#comment-257 Not having a semicolon after a function statement is ok as long as you have a newline. In a situation where we compress a js file for savings of space, using a program like yui compressor, it can cause errors. For example, try this on firebug console: <pre><code>fn=function(){console.log("hi");}a=2;</code></pre> this will show an error. Insert a semicolon after } and it will work fine. Not having a semicolon after a function statement is ok as long as you have a newline. In a situation where we compress a js file for savings of space, using a program like yui compressor, it can cause errors. For example, try this on firebug console:

fn=function(){console.log("hi");}a=2;

this will show an error.

Insert a semicolon after } and it will work fine.

]]>