Anonymous Functions: Difference between revisions
>Ozzypig Created page with "An '''anonymous function''' is a function literal that has no direct identifier. They are used in shortening code. Example {{Example| An anonymous function used with [[Connect..." |
>JulienDethurens No edit summary |
||
| Line 1: | Line 1: | ||
An '''anonymous function''' is a function literal that has no direct identifier. They are used in shortening code. | An '''anonymous function''' is a function literal that has no direct identifier. They are used in shortening code. | ||
{{Example| An anonymous function used with [[ | |||
< | ==Examples== | ||
{{Example| An anonymous function used with [[connect]]: | |||
<code lua> | |||
brick = script.Parent | brick = script.Parent | ||
brick.Touched:connect(function (part) | brick.Touched:connect(function(part) | ||
--I'm a comment in an anonymous function! | --I'm a comment in an anonymous function! | ||
print("Beep") | print("Beep") | ||
end) | end) | ||
</ | </code>}} | ||
The above code is shorter than defining a named function, like such: | The above code is shorter than defining a named function, like such: | ||
{{Example|< | {{Example|<code lua> | ||
brick = script.Parent | brick = script.Parent | ||
| Line 18: | Line 21: | ||
brick.Touched:connect(onTouch) | brick.Touched:connect(onTouch) | ||
</ | </code>}} | ||
Anonymous functions are most commonly used in [[Using_the_Chatted_Event|chat scripts]] or compound event scripts. These are used so that the arguments from the current function are still accessible. Example: | Anonymous functions are most commonly used in [[Using_the_Chatted_Event|chat scripts]] or compound event scripts. These are used so that the arguments from the current function are still accessible. Example: | ||
{{Example|< | {{Example|<code lua> | ||
game.Players.PlayerAdded:connect(function (player) | game.Players.PlayerAdded:connect(function(player) | ||
player.Chatted:connect(function (msg) | player.Chatted:connect(function (msg) | ||
--if this anonymous function was instead a named function outside of the anonymous function in the PlayerAdded connection, | --if this anonymous function was instead a named function outside of the anonymous function in the PlayerAdded connection, | ||
| Line 27: | Line 31: | ||
end) | end) | ||
end) | end) | ||
</ | </code> | ||
If you wanted to have the function in the Chatted connection to have a name, you would still have to use an anonymous function. It wouldn't need to be nearly as long as the actual message-processing code though: | If you wanted to have the function in the Chatted connection to have a name, you would still have to use an anonymous function. It wouldn't need to be nearly as long as the actual message-processing code though: | ||
< | <code lua> | ||
function onPlayerChatted(player, msg) | function onPlayerChatted(player, msg) | ||
--thanks to the anonymous function below, this function has a `player` argument | --thanks to the anonymous function below, this function has a `player` argument | ||
| Line 35: | Line 39: | ||
game.Players.PlayerAdded:connect(function (player) | game.Players.PlayerAdded:connect(function (player) | ||
player.Chatted:connect(function (msg) | player.Chatted:connect(function(msg) | ||
--message processing is in the onPlayerChatted function instead of here | --message processing is in the onPlayerChatted function instead of here | ||
onPlayerChatted(player, msg) | onPlayerChatted(player, msg) | ||
| Line 41: | Line 45: | ||
end) | end) | ||
end) | end) | ||
</ | </code> | ||
}} | }} | ||
This is useful for shortening code, however this should be avoided in code that runs more than once. This is because the function is being defined more than once, which is unneeded because it is a literal function that is unchanging. These functions should be semantically named and used as such. | This is useful for shortening code, however this should be avoided in code that runs more than once. This is because the function is being defined more than once, which is unneeded because it is a literal function that is unchanging. These functions should be semantically named and used as such. | ||
Revision as of 06:19, 27 January 2012
An anonymous function is a function literal that has no direct identifier. They are used in shortening code.
Examples
The above code is shorter than defining a named function, like such:
Anonymous functions are most commonly used in chat scripts or compound event scripts. These are used so that the arguments from the current function are still accessible. Example:
game.Players.PlayerAdded:connect(function(player)
player.Chatted:connect(function (msg)
--if this anonymous function was instead a named function outside of the anonymous function in the PlayerAdded connection,
--it would not be able to access the `player` variable
end)
end)
If you wanted to have the function in the Chatted connection to have a name, you would still have to use an anonymous function. It wouldn't need to be nearly as long as the actual message-processing code though:
function onPlayerChatted(player, msg)
--thanks to the anonymous function below, this function has a `player` argument
end
game.Players.PlayerAdded:connect(function (player)
player.Chatted:connect(function(msg)
--message processing is in the onPlayerChatted function instead of here
onPlayerChatted(player, msg)
--this function is defined much faster than the possible long message processing code
end)
end)
This is useful for shortening code, however this should be avoided in code that runs more than once. This is because the function is being defined more than once, which is unneeded because it is a literal function that is unchanging. These functions should be semantically named and used as such.
