Timeline for Trolling the troll
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 22, 2016 at 1:50 | history | edited | The Fifth Marshal | CC BY-SA 3.0 |
Syntax Highlight
|
Jan 20, 2016 at 0:01 | history | edited | Oriol | CC BY-SA 3.0 |
null is not an object
|
May 4, 2014 at 17:51 | comment | added | user344 |
UglifyJS says WARN: Dropping side-effect-free statement [-:4,11] and returns function foo(a){}for(var i=0;foo(i);++i)alert("Infinite alerts!"); .
|
|
Mar 24, 2014 at 5:12 | comment | added | SilverbackNet | Well, any minifier that changed the execution would be broken, although the leftover line split (or insertion of a semicolon) might tip a reader off. | |
Mar 18, 2014 at 9:10 | review | Suggested edits | |||
Mar 18, 2014 at 9:23 | |||||
Mar 18, 2014 at 6:31 | comment | added | Mohammed Joraid | Hoping that the troll will not minify the code! | |
Mar 13, 2014 at 22:07 | comment | added | ApproachingDarknessFish | +1. Semicolon insertion stopped me from learning JavaScript. | |
Mar 13, 2014 at 0:02 | comment | added | Dave Forber |
@NigelNquande the semicolon doesn't cause the failure, the line break does. The return and the object that is supposed to be returned are on separate lines, so the object is never returned. To "fix", remove the line break so it reads return {
|
|
Mar 12, 2014 at 21:11 | comment | added | Mara Ormston | +1 as this "flaw" in JS has caught me off guard numerous times... Had to reread it a couple times to see it | |
Mar 12, 2014 at 20:41 | comment | added | Agi Hammerthief | +1 because I work with JS on a regular basis and have looked at your code and explanation and still don't see how the semicolon causes the failure. | |
Mar 12, 2014 at 17:53 | comment | added | CompuChip | Tempted to +1 just for the use of "truly" and "falsy" ;) | |
Mar 12, 2014 at 17:40 | history | answered | Oriol | CC BY-SA 3.0 |