this(function() {
}());
or this(function() {
})();
Suicide
>>59815350
Why the fuck do you have * instead of =?
>>59815350
>babby doesn't know about type coercion
>>59815350
gotta love the NaNNaNNaNNaNNaN batman languages
>>59815330
outside wrap because it clearly expresses that you want to evaluate the whole function as one unit.
in all honesty though, IIFE is kind of cancerous and the only time I end up using it is when I'm in a template string.
also
>using function()
>not =>
lame city
>>59815330
we have module loaders now you know
>>59815350
>purposely mixing types that don't make sense
>"LOL, look at this strange output xDDD"
not an issue if you know what you're doing.
>>59815794
~function(){}()
>>59815350
If you write code like this, it is your problem, not JS.
And still, when a JS app/script breaks, at worst a browser tab has to be closed.
When a C program breaks, half of the internet is down or has major security problems.
>still using segfaulting, insecure C in this day and age
>it's the programmer's fault they said
And yet, they write shitty edge cases to "prove" how a language is bad, not the retards who write those shitty edge cases, in the first place.
>>59816254
bitwise operator on a IIFE?
what's your point?
>>59816464
Who said anything about C you insecure faggot?
>>59816568
It doesn't matter what you use as long as it's a unary operator, !function or +function works too
Whereas just function(){}() won't work
See http://stackoverflow.com/a/7586969
>>59816118
No programmer is free from mistakes. A good language would at least say "Hey dumbass, what you're doing is stupid." while JavaScript silently skull fucks your data.
Please stick your penis in a toaster before ever thinking about writing code again.
>>59816464
Apparently you don't know about js fags who are using it for server code and are even pushing to have it adopted for embedded systems.
>>59816646
No, you just lack skills
>>59816613
and your point is what exactly?
>>59816705
Save 1 byte? Idk man why are you so difficult