I bet that you wouldn't claim that if you stopped and thought about it
;-) Given how liberally you could insert parentheses into JavaScript
source code, especially as you can re-parenthesis any existing
parenthesised expression so inserting them "wherever you can" would
become recursive, you would be unlikely to ever manage to complete the
code for your first function.
The parenthesising of (and within) expressions is not really the subject
of my quibble (and it is no more than that). I also do not bother to
memorise operator precedence in languages and instead use nested
parentheses to force (and express) my desired precedence (JavaScript's
automatic type conversion often makes that doubly desirable).
My comments were more aimed at the expression of the distinction between
a function call, in which the tradition is that the opening parenthesis
is not separated from the identifier or property accessor for the
function reference (even though it could be), and the nature of typeof
and void as operators and return as a statement. Which might be better
expressed by separating the expression from the operator/statement with
at least one space.
I mentioned it mostly because I often encounter people talking of "the
typeof function", "the void function" and (though very rarely) "the
return function". That is a misconception that could not easily arise
from reading the language documentation (or books on the subject) and I
suspect that it arises in the minds of authors new to JavaScript as a
result of seeing code that uses typeof (etc) in a function call-like
formulation.
And so long as the resulting code executes nobody can stop you. But,
when posting in a group where some of the readers may reasonably be
expected to not be that experienced, would the cost of putting in the
odd extra space character to make code that represent function calls
distinct from code that is not a function call really be too much of an
inconvenience?