Question

When calling a Javascript function, it seems like JS gives priority to functions without parameters first, even if I have the same function name with parameters.
The strange behavior only happens in the following scenario:

I have a an HTML page with embedded Javascript, like this:

 //Javascript in the page  
 function testAbc(){
       alert('testAbc no params');
 }

 //Javascript in common.js
 function testAbc(x){
      alert('testAbc with param:'+x);
 }
 function testAbcFunc(x){
      testAbc(x);
 }

Now from somewhere in the page, im calling testAbcFunc from the common.js expecting it to call testAbc with parameter which is the common function. But strangely, JS calls back the function in the original page without params!!

I have been debugging this bug fore few hours now, and i tried this short code to reproduce the bug, it does happen each time.

NOTE: if all functions are in the same page, the correct function (with params) will be called, but when ther are split between the page and the JS file. JS seems to give priority to the function in the page even though is doesn’t have parameter

Answer 1

JavaScript doesn’t have overloaded function. It doesn’t care about signatures, it calls functions solely by names and nothing else. It is strange that later function does not completely hide the first one but well, there’s no spec about that behaviour.

So just don’t do that, check the number of params with arguments.length inside the function and don’t try to use overloading which will never work.

function testAbc(){
   if (arguments.length == 0) {
       alert('testAbc no params');
   } else {
       var x = arguments[0];
       alert('testAbc with param:'+x);
   }
}