Hi,
In [EMAIL PROTECTED]
Re: More info on Swig 1.31 vs 1.33 on Thu, 31 Jan 2008 13:32:58 +0900,
Kouhei Sutou [EMAIL PROTECTED] wrote:
Solution:
1) use 'vresult' instead of $result. :
2) ask for reverting the SWIG change and mark SWIG 1.3.33 as 'not supported'.
3) come up with any other
Hi Peter,
On Jan 29, 2008 5:04 PM, Peter Samuelson [EMAIL PROTECTED] wrote:
Roderich, thanks for all your hard work!
Kouhei, Joe, * - can anyone have a look at this compatibility issue
with svn + ruby + swig 1.3.33? Roderich Schupp has figured out exactly
what the problem is, but I have no
Hi,
2008/1/30, Peter Samuelson [EMAIL PROTECTED]:
%typemap(ruby, argout) apr_pool_t *pool
{
svn_swig_rb_set_pool($result, _global_svn_swig_rb_pool);
svn_swig_rb_pop_pool(_global_svn_swig_rb_pool);
}
This isn't really output parameter processing (hint: it doesn't
assign to
Hi,
I got my shovel and dug some more into these
TypeError: Expected argument 1 of type ..., but got Array [] errors.
Here's what I found (warning lengthy explanation ahead).
(1) In general, Swig tries to deliver output parameters (as viewed from
the C level) as multiple return values in the
4 matches
Mail list logo
