[Pyrex] Re: was: problem with void*....
Mike Rovner
mike at nospam.com
Fri Jun 20 22:55:33 CEST 2003
Geoffrey Bantle wrote:
> --- Greg Ewing <greg at cosc.canterbury.ac.nz> wrote:
>> Geoffrey Bantle <hairbat at yahoo.com> wrote:
>>
>>> cdef VSession createSession():
>>> cdef VSession Connection
>>> return Connection
>>
>> I hope this is just a placeholder for something
>> you're going to write
>> later, because, as it stands, it doesn't create
>> anything. It just
>> returns an uninitialised pointer.
IIUC that pointer is initialised during
vll_send_connect(char *name, char *pass, void *address, VSession *
*connection);
call where you shall pass
VSession* my_sess;
address of VSession pointer to be initialised - &my_sess.
> void vll_session_set(VSession session);
> void vll_session_destroy(VSession session);
>> With the declaration of Connection as a VSession
>> this won't work,
>> once again because Pyrex can't automatically convert
>> a void * to a
>> Python object.
That is a part I don't understand fully. Given that VSession is a pointer,
C can easily pass that (with complains about void).
> What would one do with void pointers normally?
So a proposed solution is to pass *my_sess,
but change VSession description from void to say char* to keep pyrex & C
happy.
> The triple pointer might be a mistake on Eskil's part,
> although it wouldn't make much sense considering hes
> using the same source as he gives us and has verse
Is is just a way to mark an aligned placeholder.
>> Can you point us towards any documentation for what
>> you're trying
>> to wrap?
>
> the verse 2.0 spec
>
http://www.blender.org/modules.php?op=modload&name=phpBB2&file=viewtopic&t=1501&start=0
>
> the sourceforge verse page is for verse 1.0 which is
> completley different codebase, this is the current
> information.
>
> the latest verse2 sources...
> http://www.blender.org/modules/verse/verse2.zip
It seems that VSession interface didn't changes since v1.0
Hope this helps,
Mike
More information about the Pyrex
mailing list