Luo - Revision history

Ximan: /* See Also */

2010-11-02T16:40:50Z

‎See Also

Ximan: /* Live UO Methods */

2010-11-02T07:52:49Z

‎Live UO Methods

Ximan: /* Description */

2010-11-02T07:51:47Z

‎Description

Ximan: /* Description */

2010-11-02T07:47:35Z

‎Description

Ximan: /* Live UO Methods */

2010-11-02T07:44:52Z

‎Live UO Methods

Ximan: /* Description */

2010-11-02T07:44:17Z

‎Description

Ximan: /* Description */

2010-11-02T07:42:43Z

‎Description

Ximan: /* Description */

2010-11-02T07:38:09Z

‎Description

Ximan: Created page with "== Calling Convention == Call local l = sl.luo Args n/a Result l is a table with all live uo methods == Example Usage == local l = sl.luo local waitforchange = function(ol..."

2010-11-02T07:37:49Z

Created page with "== Calling Convention == Call local l = sl.luo Args n/a Result l is a table with all live uo methods == Example Usage == local l = sl.luo local waitforchange = function(ol..."

New page

== Calling Convention ==
Call
local l = sl.luo
Args
n/a
Result
l is a table with all live uo methods

== Example Usage ==

local l = sl.luo
local waitforchange = function(old, live)
while old == live() then
wait(100)
end
end
waitforchange(UO.Sex, l.Sex)
print('Something's very wrong!')

== Description ==

luo stands for 'live uo' table, it provides [[http://en.wikipedia.org/wiki/Functor functors]] that, when called, access the underlying values from the UO table. Thus it provides a tool to pass a UO table variable name to a function and have the value retrieved at a later point in execution.

== Live UO Methods ==

There is a method for each corresponding name in the UO table. Additionally, the following methods return tables of UO values with a single call:

* [[luo.Char]]

* [[luo.Cli]]

* [[luo.Cont]]

* [[luo.Cur]]

* [[luo.LLifted]]

* [[luo.LTarget]]

* [[luo.Max]]

* [[luo.R]]

== See Also ==

* [http://www.easyuo.com/openeuo/wiki/index.php/Documentation#Variables UO Variables]

← Older revision		Revision as of 16:40, 2 November 2010
Line 45:		Line 45:

	== See Also ==		== See Also ==
		+
		+	* [http://www.easyuo.com/openeuo/wiki/index.php/Simplelib simplelib]

	* [http://www.easyuo.com/openeuo/wiki/index.php/Documentation#Variables UO Variables]		* [http://www.easyuo.com/openeuo/wiki/index.php/Documentation#Variables UO Variables]

@@ Line 26: / Line 26: @@
 == Live UO Methods ==
-There is a method for each corresponding name in the UO table.  Additionally, the following methods return tables of related UO values with a single call:
+There is a method for each corresponding name in the UO variables table.  Additionally, the following methods return tables of related UO values with a single call:
 * [[luo.Char]]

@@ Line 22: / Line 22: @@
 luo stands for 'live uo' table, and it provides [http://en.wikipedia.org/wiki/Functor functor] methods that, when called, access the underlying values from the UO table.  Thus it provides a tool to pass a UO table variable name as an argument to a function and have the associated value retrieved at a later point in execution.
-While similar functionality can be obtained by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected. Misspelled method names raise an immediate error where specified.  Thus, no special string processing/checking is obviated.
+While similar functionality can be obtained by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected, obviating the need for special string validity checking.  Additionally, misspelled methods will raise a runtime error at the point that they are specified, whereas with a string passing mechanism an error may arise nonlocally.
 == Live UO Methods ==

@@ Line 20: / Line 20: @@
 == Description ==
-luo stands for 'live uo' table, it provides [http://en.wikipedia.org/wiki/Functor functors] that, when called, access the underlying values from the UO table.  Thus it provides a tool to pass a UO table variable name to a function and have the value retrieved at a later point in execution.
+luo stands for 'live uo' table, and it provides [http://en.wikipedia.org/wiki/Functor functor] methods that, when called, access the underlying values from the UO table.  Thus it provides a tool to pass a UO table variable name as an argument to a function and have the associated value retrieved at a later point in execution.
-While similar functionality can be obtain by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected. Misspelled method names raise an immediate error where specified.  Thus, no special string processing/checking needs to be implemented.
+While similar functionality can be obtained by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected. Misspelled method names raise an immediate error where specified.  Thus, no special string processing/checking is obviated.
 == Live UO Methods ==

@@ Line 22: / Line 22: @@
 luo stands for 'live uo' table, it provides [http://en.wikipedia.org/wiki/Functor functors] that, when called, access the underlying values from the UO table.  Thus it provides a tool to pass a UO table variable name to a function and have the value retrieved at a later point in execution.
-While similar functionality can be obtain by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected, thus no special string handling needs to be implemented, and misspelled method names raise an immediate error where specified.
+While similar functionality can be obtain by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected. Misspelled method names raise an immediate error where specified.  Thus, no special string processing/checking needs to be implemented.
 == Live UO Methods ==

← Older revision		Revision as of 07:42, 2 November 2010
Line 21:		Line 21:

	luo stands for 'live uo' table, it provides [http://en.wikipedia.org/wiki/Functor functors] that, when called, access the underlying values from the UO table. Thus it provides a tool to pass a UO table variable name to a function and have the value retrieved at a later point in execution.		luo stands for 'live uo' table, it provides [http://en.wikipedia.org/wiki/Functor functors] that, when called, access the underlying values from the UO table. Thus it provides a tool to pass a UO table variable name to a function and have the value retrieved at a later point in execution.
		+
		+	While similar functionality can be obtain by passing around strings, the live uo methods have the advantage of being of type 'function' and passing argument checks where functions are expected, thus no special string handling needs to be implemented, and misspelled method names raise an immediate error where specified.

	== Live UO Methods ==		== Live UO Methods ==