Re: [Chicken-users] SWIG and 2.5rc1

[felix winkelmann]

On 10/11/06, John Lenz <address@hidden> wrote:
> I tried running the 2.5rc1 against the latest SWIG code (which we are
> about to make a rc release too... good test of them both).  Problem is,
> when you use the -proxy argument to SWIG it exports
>
> (declare (uses tinyclos))
>
> into the generated .scm file.  This won't work anymore unless -uses
> tinyclos is passed on the command line, and I am not sure how it will
> work if you try with csi.
>
> So I was wondering if it should be changed to (require-extension)?
> Problem is, it needs to be backwards compatible.  Will require-extension
> work on old versions of chicken?..  maybe just (require)? Or should I
> change SWIG to export some code to test the chicken version?

"(require-extension tinyclos)" will do the right thing on new and old
versions of chicken. On old versions, tinyclos is builtin and the form
will expand into a "(declare (uses tinyclos))". On newer chickens,
it will expand into the proper code to load the tinyclos macros at
compile-time and the support code at runtime.


cheers,
felix

--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp