From: Michael O'Connor <moconnor59@ya...> - 2004-03-16 17:38:03
That works, in that the called function returns values
correctly to the Lisp interpreter, but my called
function is not receiving any arguments from the Lisp
interpreter other that the context (closure) data.
Do I need to do something in the call to
cl_make_cclosure_va() to indicate the number of
arguments the callback function is expecting (similar
to the nargs argument to cl_def_c_function())?
--- worm <worm@...> wrote:
> ATTACHMENT part 1 message/rfc822
> From: worm <worm@...>
> To: Michael O'Connor <moconnor59@...>
> Date: Thu, 11 Mar 2004 15:20:37 GMT
> Subject: Re: [Ecls-list] cl_def_c_function()
> Remitente: Michael O'Connor <moconnor59@...>
> > Quick question (I hope): does ECL support the idea
> > "client callback data"? By this I mean a C void
> > pointer (void *) or similar that can be used to
> > / refer to context data in calls to the C/C++
> > application.
> Not really. You can implement something similar
> not def_c_function, but closures. However, right now
> the data associated to the closure should be wrapped
> in a lisp object. For an example, have a look at
> si_hash_table_iterator and si_hash_table_iterate.
> Basically, the idea is that the data of the closure
> passed as a first argument to the called function.
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam