Adam is right; both functions return undefined, and in any case, it is absolutely normal if you do not care about the return value (or want the value to be undefined). However, often in more complex programs there is often an explicit return from a function, especially since Javascript programs often have complex callback mechanisms. For example, in this piece of code (a little more complicated than yours), I believe that the return statement really helps clarify the code:
function someAsyncFunction(someVar, callback) { // do something, and then... callback(someVar); // will return undefined return; } function c(){ var someState = null; if (some condition) { return someAsyncFunction(some variable, function () { return "from the callback but not the function"; }); // we've passed the thread of execution to someAsyncFunction // and explicitly returned from function c. If this line // contained code, it would not be executed. } else if (some other condition) { someState = "some other condition satisfied"; } else { someState = "no condition satisfied"; } // Note that if you didn't return explicitly after calling // someAsyncFunction you would end up calling doSomethingWith(null) // here. There are obviously ways you could avoid this problem by // structuring your code differently, but explicit returns really help // avoid silly mistakes like this which can creep into complex programs. doSomethingWith(someState); return; } // Note that we don't care about the return value. c();
source share