Most sites say callee as a property of Function.prototype.arguments is deprecated. But some sites go further and say the whole of Function.prototype.arguments is deprecated E.g. https://web.archive.org/web/20130313045745/http://aptana.com/reference/api/Arguments.html . Why only mention callee if the whole routine is dead in the water? I only just discovered arguments and it seems incredibly useful E.g: http://hungred.com/how-to/secret-arguments-array-javascript/
Add a comment
|
5 Answers
Function.prototype.arguments is deprecated, but it's only deprecated in favor of the vanilla arguments object that's available within a function. (e.g. using x = arguments[i]; instead of x = theFunc.arguments[i];)
That's now the preferred (and as you say, extremely useful) method for accessing the ordinal arguments received.
3 Comments
Stijn de Witt
This makes sense. If Javascript ever wants some multi-threading support, such global stateful objects are killing.
doubleOrt
Why is
Function.arguments deprecated though ? It allows you to directly access the arguments of a parent function inside of a nested function, this is something you can't do with the arguments object.
Zack Morris
I posted workaround
getArguments() functions for Node.js and browser due to this lack of functionality at stackoverflow.com/a/49544338/539149Afaik arguments is deprecated as a property of Function. See this MDN-link, or this one
Comments
The Javascript "argument array" — not deprecated, but I would say outdated as of 2021:
The “arguments” keyword is reserved and cannot be used as a parameter name or within the function body as a local variable. This feature was designed to allow an arbitrary amount of arguments when invoking a function without having to specify an arbitrary amount of parameters in the function definition. It is also an outdated way to utilize multiple arguments and is less efficient than the modern rest parameters method.
Here is an example showing preferred practice:
function eat(...food) {
for (let item in food) {
console.log("eating " + item);
}
// log the rest parameter
console.log(food);
}
eat("eggs", "toast", "bacon");
// => eating eggs
// => eating toast
// => eating bacon
// => [ 'eggs', 'toast', 'bacon' ]
The above quote and code sample are from an article titled JavaScript Parameters and Arguments
Comments
callee is deprecated, but the arguments is used in many applications. I don't know if arguments is deprecated. You can use it to get all the parameters of a function, even if there not defined within function( params ).
Most of the time I used when I develop a jQuery plugin. Something like:
$.fn.tooltip = function( method ) {
if ( methods[method] ) {
return methods[method].apply( this, Array.prototype.slice.call( arguments, 1 ));
} else if ( typeof method === 'object' || ! method ) {
return methods.init.apply( this, arguments );
} else {
$.error( 'Method ' + method + ' does not exist on jQuery.tooltip' );
}
};
As you can see only method is passed as a parameter, but within the first if the arguments is split after the first value. This way you can pass a function name, and all parameters used by this function.
Full example: http://docs.jquery.com/Plugins/Authoring
Comments
No, the arguments array is not deprecated in the latest 5.1 version of the specification (see page 60). The caller object will however only be available if the code is not in strict mode.
