No subject
Sun Feb 20 15:14:05 GMT 2011
main file to study in this regard.
James mentioned "SWIG C# supports directors, meaning that user code written
in C# can be passed as callbacks to some parts of Xapian, so it would good
to provide some examples of this". With this, I understand that you need
examples of c# code passing as callbacks to Xapian. Is it right?
Could you please specify what do you mean by "idioms" as this is a new term
for me. What I understand that it means close to the target language like
e.g., if there is a wrapper for c#, the wrapper should make the user feel as
writing in c#?
Olly mentioned "One obvious think to look for: anything that gets wrapped as
something
involving SWIGTYPE really needs addressing". It means that this is the first
task to start with.
Also, I did agree with Olly that Java bindings could be improved too as C#
and Java are quite similar. I have more than 1 year of JAVA experience.
Regards
Rauf
On 21 March 2011 16:55, James Aylett <james-xapian at tartarus.org> wrote:
> On 21 Mar 2011, at 14:51, Olly Betts wrote:
>
> >> (in a subdirectory; there are two main files, util.i and
> >> extra.i; generally speaking util.i is for SWIG "typemaps", which
> >> convert arguments between the target language and C++, while extra.i
> >> is currently only used by the python bindings to inject additional
> >> python code, mostly to provide more idiomatic iterators).
> >
> > I think the main reason for the two is that we need to include them at
> > different points in the interface file, but it has been a while since
> > I worked on the overall structure.
>
> I'm pretty sure I introduced that split, and that's certainly the reason I
> remember.
>
> > If the scope of improving the C# bindings seems too narrow to keep you
> > busy for the Summer, you could usefully look at Java too, if you're also
> > familiar with that. SWIG's support for C# and Java works in very
> > similar ways (they were written and are maintained by the same person)
> > so quite a lot would be in common.
>
>
> Getting the SWIG Java bindings finished would be awesome.
>
> J
>
> --
> James Aylett
> talktorex.co.uk - xapian.org - devfort.com
>
>
--001636ed7099aa335a049f0175b1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div>Hi Olly and James,</div><div><br></div><div>Thanks for your replies.</=
div><div><br></div><div>From your posts, I understand that I first need to =
study SWIG. Util.i is the main file to study in this regard.</div><div><br>
</div><div>James mentioned "SWIG C# supports directors, meaning that u=
ser code written in C# can be passed as callbacks to some parts of Xapian, =
so it would good to provide some examples of this". With this, I under=
stand that you need examples of c# code passing as callbacks to Xapian. Is =
it right?</div>
<div><br></div><div>Could you please specify what do you mean by "idio=
ms" as this is a new term for me. What I understand that it means clos=
e to the target language like e.g., if there is a wrapper for c#, the wrapp=
er should make the user feel as writing in c#?</div>
<div><br></div><div>Olly mentioned "One obvious think to look for: any=
thing that gets wrapped as something</div><div>involving SWIGTYPE really ne=
eds addressing". It means that this is the first task to start with.</=
div>
<div><br></div><div>Also, I did agree with Olly that Java bindings could be=
improved too as C# and Java are quite similar. I have more than 1 year of =
JAVA experience.</div><div><br></div><div>Regards</div><div>Rauf=A0</div>
<br><div class=3D"gmail_quote">On 21 March 2011 16:55, James Aylett <span d=
ir=3D"ltr"><<a href=3D"mailto:james-xapian at tartarus.org">james-xapian at ta=
rtarus.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On 21 Mar 2011, at 14:51, Olly Betts wrote:<br>
<br>
>> (in a subdirectory; there are two main files, util.i and<br>
>> extra.i; generally speaking util.i is for SWIG "typemaps"=
;, which<br>
>> convert arguments between the target language and C++, while extra=
.i<br>
>> is currently only used by the python bindings to inject additional=
<br>
>> python code, mostly to provide more idiomatic iterators).<br>
><br>
> I think the main reason for the two is that we need to include them at=
<br>
> different points in the interface file, but it has been a while since<=
br>
> I worked on the overall structure.<br>
<br>
</div>I'm pretty sure I introduced that split, and that's certainly=
the reason I remember.<br>
<div class=3D"im"><br>
> If the scope of improving the C# bindings seems too narrow to keep you=
<br>
> busy for the Summer, you could usefully look at Java too, if you'r=
e also<br>
> familiar with that. =A0SWIG's support for C# and Java works in ver=
y<br>
> similar ways (they were written and are maintained by the same person)=
<br>
> so quite a lot would be in common.<br>
<br>
<br>
</div>Getting the SWIG Java bindings finished would be awesome.<br>
<div><div></div><div class=3D"h5"><br>
J<br>
<br>
--<br>
=A0James Aylett<br>
=A0<a href=3D"http://talktorex.co.uk" target=3D"_blank">talktorex.co.uk</a>=
- <a href=3D"http://xapian.org" target=3D"_blank">xapian.org</a> - <a href=
=3D"http://devfort.com" target=3D"_blank">devfort.com</a><br>
<br>
</div></div></blockquote></div><br>
--001636ed7099aa335a049f0175b1--
More information about the Xapian-devel
mailing list