[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: log_receiver in swig bindings

From: Russell Yanofsky <rey4_at_columbia.edu>
Date: 2003-07-17 20:30:25 CEST

Chia-liang Kao wrote:
>...
> while there is an issue with the current swig interface definition.
> the gluing callback thunk_receiver tries to create a object of
> svn_log_changed_path_t * for the target language. But it was declared
> in svn_types.c, which all its wrappers are created in core.i. while
> the thunk_receiver is working under namespace of svn_repos, it can't
> resolve svn_log_changed_path_t * in runtime.

Actually the problem is this line in core.i:

  %ignore svn_log_changed_path_t;

I posted a small patch to fix this and the swigutil_py problem a little while
ago but nobody responded and hasn't it been committed. It's at
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=40022

- Russ

> my current workaround
> is to paste the struct definition into svn_repos.i, before %import
> svn_types.i. but this is definitely not the way since there are
> probaby other cases like this. one possible solution is to build
> all wrapper in one package, and each module just imports the symbols
> it is interested in. another way is to move the typedef into
> svn_repos.h.
>
> btw, in swigutil_py.c:svn_swig_py_thunk_log_receiver, it tries to
> resolve SWIGTYPE_p_svn_log_changed_path_t instead of
> svn_log_changed_path_t *.
>
> Cheers,
> CLK
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 17 20:31:30 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.