[Quantlib-dev] Fwd: Re: R-SWIG-Quantlib status report

[Joseph W. <jo...@gn...>]

Apologies if this is a duplicate, but the original message doesn't seem to=
=20
have made it to the sourceforge list.

=2D---------  =E8=BD=AC=E5=8F=91=E7=9A=84=E4=BF=A1=E4=BB=B6  ----------

Subject: Re: R-SWIG-Quantlib status report
Date: Wednesday 03 May 2006 13:56
=46rom: Joseph Wang <jo...@gn...>
To: William S Fulton <ws...@fu...>
Cc: Duncan Temple Lang <du...@wa...>, Dirk Eddelbuettel=20
<ed...@de...>, Luigi Ballabio <lui...@gm...>, swig-devel=20
<swi...@li...>

Just an update.

I got RSwig integrated with the test-suite, and after about two weeks of
 work, it currently compiles about 85% of the test cases.  The test cases
 which it doesn't compile seem not to be too difficult to fix.  They involve
 things like the fact that R doesn't like "in" as a variable name or has
 difficulties with functions that start with a _.

I was wondering what remains to be done in order to get R-Swig integrated
 with the mainline SWIG tree.  The current version in my tree seems to have
 all of the features that were in Prof. Temple Lang's version except for the
 copy to and from R functionality and that was excluded because it wasn't
 obvious how this would work with complex C++ data structures.  Also,
 assuming that there are not any major design issues, then I think that it
 would be useful to have R-Swig available in the SWIG distribution so that
 there is a wider audience for big fixing.  Assuming that there are no desi=
gn
 issues, I think R-SWIG is also at a point at which what is broken can be
 tracked with a bug tracking system.

If I could get a TODO list of the things that need to be done and design
issues that need to be resolved before R-Swig is integrated into the main
source tree, I can start working on those.

=2D------------------------------------------------------