>> First: Would you be so kind and stop talking in third person about me >> when I'm around? Thank you. > > I'm sorry. I think I wanted to write "this", not "his". That probably looked > a bit offensive. :(
:-) And maybe I was just too thin-skinned. >> Second: I know that this requires to intend the rest of the code. >> >> But what I really want to know is about technical reasons, not style. >> I want to know if it makes any difference to the JIT, v8, or whatever >> stacks around. Is not using return an improvement, an deterioration or >> does it make no difference for performance/code optimization. >> >> So, under the scope of the question of the OP: What about not using return? > > If you're concerned that much about speed, you might want to hack in C or so. > :D And if > you believe in microbenchmarks: http://jsperf.com/return-vs-no-return I'm not really concerned, just curious. And if I would believe in the benchmarks you mentioned, than I had to say that there is no definite answer. BTW: It comes from python, where they say: Do not return early, use if else. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
