GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — javascript/JavaScript-Style/Control-Statement.js at main · ankityv/javascript Expand file tree/ Copy pathControl-Statement.jsMore file actions 56 lines (45 loc) · 1.13 KB / Copy pathControl-Statement.jsFile metadata and controls56 lines (45 loc) · 1.13 KB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 //: 17.1 => /* In case your statement (if, while etc) gets too long or exceeds the maximum line length, each (grouped) condition could be put into a new line. The logical operator should begin the line. */ /* Why? Requiring operators at the beginning of the line keeps the operators aligned and follows a pattern similar to method chaining. This also improves readability by making it easier to visually follow complex logic. */ // bad if ( (foo === 123 || bar === "abc") && doesItLookGoodWhenItBecomesThatLong() && isThisReallyHappening() ) { thing1(); } // bad if (foo === 123 && bar === "abc") { thing1(); } // bad if (foo === 123 && bar === "abc") { thing1(); } // bad if (foo === 123 && bar === "abc") { thing1(); } // good if (foo === 123 && bar === "abc") { thing1(); } // good if ( (foo === 123 || bar === "abc") && doesItLookGoodWhenItBecomesThatLong() && isThisReallyHappening() ) { thing1(); } // good if (foo === 123 && bar === "abc") { thing1(); } //: 17.2 => Don't use selection operators in place of control statements. // bad !isRunning && startRunning(); // good if (!isRunning) { startRunning(); } |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |