Unless I'm mistaken 'do_something_else()' won't get executed if toggleClass() returns a value that evaluates to true. Because of short-circuit boolean evaluation.
Re:Of parser-fetishists and semi-colons
by philipjrose on Monday April 16, 2012 @03:21PM
(#3848886)
That's correct. You could use:
!isActive && ($parent.toggleClass('open'), do_something_else())
but I don't think anyone would advise it.Actually, you are all missing Crockford's real point, which is that they are considering making ! a binding deference of function objects. If they do, then this:
clearMenus()
!isActive && $parent.toggleClass('open')
Becomes this: clearMenus()!isActive && $parent.toggleClass('open');
And not this: clearMenus();
!isActive && $parent.toggleClass('open');
The no semi-colon crowd is ridiculous. There are no good arguments for omitting semicolons!Why has this been downvoted? If you don't agree, try commenting - don't downvote! Sheesh?
there are even fewer good arguments for changing the semantics of the fucking logical negation operator 17 years down the line in a dynamic language with billions of end users and no discrete versioning
About as logical as using the logical negation operator for a purpose other than logical negation. :-)
So, how would you implement this dereferencing feature? given that this wouldn't be an issue if you added a semicolon, not sure why you are so hetup there...
This actually reminds me of some cool hacks with structure pointers and functions in the Linux kernel.