Re: Miscellaneous Ruby questions

Sorry for late.
# There was my family's unhappiness last week.

In <12e601c52e83$95003760$e6ec6f83@robinson.cam.ac.uk>
  "Miscellaneous Ruby questions" on Tue, 22 Mar 2005 02:05:03 -0000,
  "Max Bowsher" <maxb@ukf.net> wrote:

> apr.i:
>
> The "#pragma SWIG nowarn=801":
> Am I correct in thinking this is just because SWIG is being rather
> excessively verbose by default?

Yes.

> Perhaps this pragma deserves a comment
> explaining its purpose.

I did.

> The "for SWIG bug" typemaps:
> Is the bug fixed?

Yes. I noticed now.

  http://sourceforge.net/tracker/index.php?func=detail&aid=1096981&group_id=1645&atid=101645

> Which versions of SWIG contain the bug?

SWIG 1.3.24 or older.

> Please wrap these
> hotfixes in an #ifdef specifying the versions they are needed for.

OK.

> core.i:
> What is the purpose of the unusual arrangements made for
> svn_stream_{read,write,close} ?

This is for making a stream in svn_swig_rb_make_stream().

> svn_client.i:
> This typemap:
> %typemap(ruby,in) (svn_client_get_commit_log_t log_msg_func)
> makes reference to "arg1". I don't think that's a rather fragile thing to
> do.

I added a comment.

> Also, "log_msg_batton" is misspelt.

Thanks. I fixed.

> svn_types.i:
> Why REMOVE_DESTRUCTOR?
> How does this relate to the %nodefault swig directive? Is that directive
> broken for ruby? It didn't appear to have any effect when I tried to use it.

I didn't know %nodefault directive.
I tried this instead of REMOVE_DESTRUCTOR now. Then I got
a segmentation fault in "make check-swig-rb".

I'll check this.

> And an overall point:
> The ruby bindings don't work with SWIG 1.3.25-dev.

I'll fix soon.

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org