Lines Matching full:invocation
20 the user_data pointer which is passed to the callback upon invocation of the closure
49 Invocation (<function><link linkend="g-closure-invoke">g_closure_invoke</link></function>): this is what closures
50 were created for: they hide the details of callback invocation from the
55 closure invocation, closure invalidation and closure finalization. Listeners
59 <function><link linkend="g-closure-add-marshal-guards">g_closure_add_marshal_guards</link></function> (invocation notification).
62 <function><link linkend="g-closure-remove-invalidate-notifier">g_closure_remove_invalidate_notifier</link></function>) but not for the invocation
112 As was explained above, closures hide the details of callback invocation. In C,
113 callback invocation is just like function invocation: it is a matter of creating
160 is used to have Python-based callback be invoked by the closure invocation process).
243 accumulator_data: this pointer will be passed down to each invocation of the
408 The accumulator function is invoked in all states, after invocation
