Search results
From LSWiki
You searched for Closures
There is no page titled "Closures". You can create this page.
For more information about searching LSWiki, see Searching LSWiki.
Showing below 14 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500).
Article title matches
- Man closures (10,783 bytes)
3: Closures provide a means of creating code dynamically and
9: The simplest kind of closures are efuns, lfuns or operators.
30: Inline closures are a variant of lfun closures, the difference being
55: Inline closures may also nested, so that the following (not very
64: The notation of inline closures is modelled after the MudOS
Page text matches
- Chats (4,471 bytes)
7: ...our chats (easier) or by writing custom functions/closures (harder).
48: ==Custom Commands and Closures in Chats==
50: There are any number of reasons to use [[closures]] in chats. The simplest case is that you want a ... - Man mappings (14,221 bytes)
9: or closures aren't a good choice because comparision between ...
327: Mappings can't use lfun or identifier closures as keys. This
335: [[man alists|alists(LPC)]], [[man closures|closures(LPC)]], [[man mkmapping|mkmapping(E)]], [[man wal... - Man modifiers (6,849 bytes)
20: with call_other(). It is possible to create #' closures
184: [[man closures|closures(LPC)]], [[man inheritance|inheritance(LPC)]], [[m... - Man closure guide (27,741 bytes)
1: ==Introduction, Overview and Efun-Closures==
13: especially of interest within lambda-closures (see below).
29: What are closures good for? With closures you can make much more univer-
100: ==Lfun- and Lambda-Closures==
102: Very often the possibilities closures to efuns offer are not sufficient - Man closures (10,783 bytes)
3: Closures provide a means of creating code dynamically and
9: The simplest kind of closures are efuns, lfuns or operators.
30: Inline closures are a variant of lfun closures, the difference being
55: Inline closures may also nested, so that the following (not very
64: The notation of inline closures is modelled after the MudOS - Man element (17,175 bytes)
238: to cloned objects, many closures) may be lost at some point. Also, do not - Man input core (6,532 bytes)
134: ...fault value from the specified dialog, evaluating closures - Man special attack (17,964 bytes)
15: Fields below which can be given as closures receive either standard
21: 4) the character. All closures are expected to return a value that could - Man hooks (concepts) (16,865 bytes)
10: unbound lambda closures as values, some also lfun closures or
61: ...ter creation. Hook setting can be unbound lambda closures, or the name of the function to call in the objec...
85: ...et an object. Hook setting can be unbound lambda closures, or the name of
116: second. Lambda closures are also bound to the object prior to the
163: Lambda-closures are additionally bound to the command_giver. - Man selection (26,617 bytes)
509: to any closures you use, as described in Closure Arguments above....
511: your closures will receive as one of their arguments a mapping ... - Man selection core (10,824 bytes)
130: user-defined closures encountered by the parser. Customarily, the opti... - Man populace (6,851 bytes)
82: home array are closures, they will be resolved, being passed an argument - Man chatter (5,013 bytes)
15: ..., the elements of this can also be closures. The closures will be given
36: closures in chatter?
44: pre-built closures in /lib/chatter_conditions.h which will cause the...
108: ===More on closures===
112: The closures can be combined using the Combine(a,b) closure as...
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500).
