Nil: Difference between revisions
>Camoy nice edits Ozzy, you can use the shortcuts though :3 |
>PurpleKiwi Fixed another "it's" mistake |
||
| Line 5: | Line 5: | ||
===Use Cases=== | ===Use Cases=== | ||
'''Nil''' can be used to blank the value of a property of an object (this can only be done with Instance-type properties; you cannot do this to number properties). It is very common to set the [[Parent]] of an object to '''nil''', which removes it from the game. However, it is possible to bring the object back. For example, if the object is referenced by a [[variable]], you can set | '''Nil''' can be used to blank the value of a property of an object (this can only be done with Instance-type properties; you cannot do this to number properties). It is very common to set the [[Parent]] of an object to '''nil''', which removes it from the game. However, it is possible to bring the object back. For example, if the object is referenced by a [[variable]], you can set its Parent property again and bring the object back. | ||
{{Example|''Example script of referencing an object.'' | {{Example|''Example script of referencing an object.'' | ||
Revision as of 00:59, 13 July 2011
Nil
What is Nil?
By definition, nil is a state of non-existence or nothingness. In Lua, nil is a non-initialized value, or lack of a value that is equal to nothing. Math cannot be performed on nil or anything equivalent to nil, because nothing, unlike 0, is not a numerical value. When an object is deleted, using the Remove function, it is removed from the game completely by setting its parent to nil. Unless the object is referenced, it cannot be recovered.
Use Cases
Nil can be used to blank the value of a property of an object (this can only be done with Instance-type properties; you cannot do this to number properties). It is very common to set the Parent of an object to nil, which removes it from the game. However, it is possible to bring the object back. For example, if the object is referenced by a variable, you can set its Parent property again and bring the object back.
p = Instance.new("Part") -- Create a new brick
p.Parent = game.Workspace -- The part (a grey brick, by default) has a parent, the workspace
wait(1)
p.Parent = nil -- The part now has no parent (and so it disappears from view, but not from memory).
wait(1)
p.Parent = game.Workspace -- part still exists because it is referenced by the variable 'p'
wait(1)
p.Parent = nil -- part disappears again (it has no parent)
p = nil -- part is no longer referenced by anything, so it gets picked up by the garbagecollector
Look through the comments in the script above to understand why recovering an object by reference is possible.
Here are more examples of "nil" usage:
game.Workspace.Player.Humanoid.Health = nil
Using the script above will have the same effects as the following script:
game.Workspace.Player.Humanoid.Health = 0
This occurs because setting a players health to "nil" will cause the player to have nothing as a health. Because nothing is similar to having no health at all, your health will go to 0 and the humanoid will die.
