**** BEGIN LOGGING AT Sat Sep 22 02:59:59 2012
Sep 22 03:36:03 <fxspec06> what happens in javascript when you return something that doesn't return something? is that, a not very good thing to do?
Sep 22 03:36:38 <fxspec06> i.e., for an if statement, i can do if (x) {y(); return;}.... or i can do if (x) return y();
Sep 22 03:37:09 <fxspec06> does it matter what happens to the return statement? javascript engine wise?
Sep 22 09:07:01 <katratxo> fxspec06: if you don't return anything specific your function returns undefined
Sep 22 14:33:24 <fxspec06> i guess what i'm asking isn't that but more of a deeper javascript question. is it poor practice to do that way
Sep 22 14:34:03 <fxspec06> it's just a method to execute a function and return exit the current function in one statement
Sep 22 15:16:00 <sugardave> perfectly fine to do that
Sep 22 15:16:16 <sugardave> functions shortcut out with returns all the time
Sep 22 15:16:42 <sugardave> sometiems some logic branch in the function will just return, while another branch will return a value, etc.
Sep 22 15:16:51 <fxspec06> fantastic. i gotta make sure the JS gods don't smite me
Sep 22 15:17:19 <sugardave> off to mail expense reports
Sep 22 15:17:20 <sugardave> whee!
Sep 22 15:17:33 <fxspec06> yippee (i think)
**** ENDING LOGGING AT Sun Sep 23 02:59:58 2012