20,741
edits
Nasal Callbacks Explained: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Template:Nasal Navigation}} | {{Template:Nasal Navigation}} | ||
Many Nasal functions accept callbacks as function arguments, i.e. you can basically pass around functions as arguments (and return values). Some of the more common uses in FlightGear are callbacks invoked by timers or by listeners. So a callback parameter is basically a "pointer" (reference) to a function. The function can be free-standing, i.e. bound to a symbolic name - or an anonymous function, that is directly specified "inline", without any name: | Many Nasal functions accept callbacks as function arguments, i.e. you can basically pass around functions as arguments (and return values). Some of the more common uses in FlightGear are callbacks invoked by timers or by listeners. So a callback parameter is basically a "pointer" (reference) to a function. The function can be free-standing or part of some other data structure (vector/hash), or a method call, i.e. bound to a symbolic name - or an anonymous function, that is directly specified "inline", without any name: | ||
Consider the following snippet of code, which assigns a function to the say_hello symbol: | Consider the following snippet of code, which assigns a function to the say_hello symbol: | ||