diff options
author | Søren Sandmann Pedersen <sandmann@daimi.au.dk> | 2009-04-14 21:07:18 -0400 |
---|---|---|
committer | Søren Sandmann Pedersen <sandmann@daimi.au.dk> | 2009-04-14 21:07:18 -0400 |
commit | dc9f4ee427f87f4d9b15d3368f05ce31b6b4f516 (patch) | |
tree | c9cb6f2c5dabbb38efd43cb2f64b0211bd715c11 | |
parent | 4c560fb4ab6c5d91a2797dfb772be0a6a1cf161c (diff) |
TODO
-rw-r--r-- | TODO | 25 |
1 files changed, 25 insertions, 0 deletions
@@ -89,6 +89,26 @@ it. Ie., the NUL_CALLBACK would do something like this: where free_callback_info would free the closure and the callback info plus any other house keeping. +Actually, we probably don't even need libffi closures. Instead +NUL_CLOSURE() creates a nul_closure_t that contains the function, the +types and the arguments. The caller of the closure is then responsible +for supplying extra arguments and for destroying it. + +There will need to be functions + + nul_create_closure (function, n_args, ...); + + /* These functions would take care of storing/overwriting/destroying */ + nul_closure_own (closure **closure, closure *closure); + nul_closure_disown (closure **closure); + + /* tie the lifetime of the closure to the object */ + nul_object_own_closure (object, closure **closure); + + /* Takes any additional argument. These are added to the front + * of the parameter list followed by all the other + */ + nul_closure_call (closure, ...); Dbus: @@ -115,6 +135,11 @@ will probably have to be specified in some other ways. One question is if it is only the specification or also the actual types that are different. +Or possibly make sfile use anonymous types. + +Why do we not need names for the introspection types? The parameter +names would be quite useful actually. + Things from glib: |