some alternative: /* curly braces inside the case */ const i = 1 switch (i) { case 0: { let x = 2342; let s = 1 + x; console.log(x+’ & ‘+s+’ from inside’); } break; case 1: { let x = 2342; let s=”b”; console.log(x+’ & ‘+s+’ from inside’); /* 2342 & b from … Read more
What’s wrong with the “else” clause ? for filename in files: try: im = Image.open(os.path.join(dirname,filename)) except IOError, e: print “error opening file :: %s : %s” % (os.path.join(dirname,filename), e) else: print im.size Now since you’re in a loop, you can also use a “continue” statement: for filename in files: try: im = Image.open(os.path.join(dirname,filename)) except IOError, … Read more
Yes, blocks are going to replace IEFEs, as soon as block-scoped declarations (functions, let/const/class) become widely adopted. You need a scope, e.g. for a closure? Here you have a block, be it a loop body or just part of a statement list. However, there is still one application of IEFEs that blocks cannot replace: the … Read more
Edit: this Half considers you are using EJS on server side 1) You can pass an ejs variable value to a Javascript variable <% var test = 101; %> // variable created by ejs <script> var getTest = <%= test %>; //var test is now assigned to getTest which will only work on browsers console.log(getTest); … Read more
This is a technique used by the JavaScript engine called hoisting. The parser will read through the entire function before running it, and any variable declarations (i.e. using the var keyword) will be executed as if they were at the top of the containing scope. So your code behaves like: var country; var i; country … Read more
With the code you have provided test will still be in scope inside the callback. xhr will not be, other than xhr.responseText being passed in as data. Updated from comment: Assuming your code looks something like this: for (var test in testers) getFileContents(“hello”+test+”.js”, function(data) { alert(test); }); } As this script runs, test will be … Read more
Classes and functions are different, variables inside a class are actually assigned to the class’s namespace as its attributes, while inside a function the variables are just normal variables that cannot be accessed outside of it. The local variables inside a function are actually decided when the function gets parsed for the first time, and … Read more
This code is not valid. It was a bug in g++ that it accepted the code. See “g++ does not treat injected class name correctly.” The bug was resolved as fixed in 2009, so it should be fixed in any recent version of g++.