Talk:IfElse: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 37: | Line 37: | ||
[[User:Ccw|MrSmartArse]] 08:46, 4 June 2009 (CEST) | [[User:Ccw|MrSmartArse]] 08:46, 4 June 2009 (CEST) | ||
---- | ---- | ||
it returns true because one of the two first arguments are false. | |||
this is lua's fault. | |||
[[User:Flobu|Flobu]] 11:43, 4 June 2009 (CEST) |
Revision as of 09:45, 4 June 2009
There's not really any use for this, as far as i can tell. Lua supports this by its syntax sugars:
moo = (variable) and (ifTrue) or (ifFalse)
works the same as
moo = (varible) ? ifTrue : ifFalse
in C++.
oO You're right. Never thought of that. What I was thinking about, too, was something like
moo = ({ [true] = ifTrue, [false] = ifFalse })[condition]
But your code is much better. Thanks for posting this. ;D NeonBlack 22:00, 18 May 2009 (CEST)
The problem with the plain Lua version is that 'ifTrue' is also part of the test condition. Consider this:
variable = true ifTrue = false ifFalse = true moo = (variable) ? ifTrue : ifFalse == false
ElseIf works fine here:
moo = IfElse( variable, ifTrue , ifFalse ) == false
Lua's and's 'n' or's however may give unexpected results:
moo = (variable) and (ifTrue) or (ifFalse) moo == true
MrSmartArse 08:46, 4 June 2009 (CEST)
it returns true because one of the two first arguments are false.
this is lua's fault.
Flobu 11:43, 4 June 2009 (CEST)