SWIG

used this as a basis to support the older and newer versions. For
swig-1.3.39.

In order for this patch to be considered, please modify it with some
backwards compatibility in it. This is the approach we use for all the SWIG
modules. We might drop older versions of a target language when they are
really old and the maintenance is too much of a burden. 352 is shipped with
an 18 month old version of Linux, so it'll still be in wide use.

Your "fairly modern development environment" uses a PLT version that is
two years old. I have tested that Dmitry's patch works for version 372 and
up. To build PLT-352 I would probably have to downgrade my entire
toolchain.

I wonder how you would feel about someone using a two years old version of
swig.

Adding support for modern versions is great, but the version that comes
with my fairly modern development environment will be broken by the patch.
A patch that works with both is what is really required.

Indeed, the `dynext/link` module naming scheme was introduced in
_recent_ versions of PLT, which this patch aims to support. 352 is an
outdated one. I believe that compatibility with _modern_ MzScheme
versions is a SWIG goal.

Unfortunately this patch breaks thinkgs. With the patch I get:

checking for mzscheme... /usr/bin/mzscheme
checking for mzc... /usr/bin/mzc
checking for MzScheme dynext object... require: unknown module:
dynext/link
Welcome to MzScheme version 352, Copyright (c) 2004-2006 PLT Scheme Inc.
>
checking for ruby... ruby

When I normally get:

checking for mzscheme... /usr/bin/mzscheme
checking for mzc... /usr/bin/mzc
checking for MzScheme dynext object... /usr/lib/plt/mzdyn.o
checking for ruby... ruby