Richard Fateman <fateman at eecs.berkeley.edu> writes:
> If you assume SBCL, then you can use its foreign function interface
> http://www.sbcl.org/manual/Introduction-to-the-Foreign-Function-Interface.html#Introduction-to-the-Foreign-Function-Interface
> to directly link to FORTRAN.
Or maybe try to use CFFI, which gives you a better chance of being able
to port your work to other lisps.
>
> On the other hand, SBCL support for Windows, according to this page
> http://www.sbcl.org/platform-table.html is "port in progress" so it
> appears SBCL is not supported on the operating system used by the vast
> majority of Maxima users.
The good news is that SBCL works fine on Windows in practice. I think
that in theory there's some racy timing bug or something that they
were/are worried about (at least, there used to be a bizarre warning
about a "kitten of death" when you started it...). I think you should
take the orangey box to mean that, while they have something that works,
they also have unincorporated patches that might make everything much
better. That said, SBCL's definition of "mostly works" is still streets
ahead of what GCL can do...
> Another possibility is to examine UFFI to see if that can be used with
> most of the common lisps.
> There may be some objection from some people to the idea of having
> FORTRAN code compiled into
> binary somehow included in Maxima. I think it is worth it, not to
> deny the possibility of difficulties regarding
> which FORTRAN compiler etc etc. I dislike the idea of relying on
> awk, perl, make ... all of whose functions should be done in Common
> Lisp...
Well, another solution would be to use ASDF or the like to make it
something that can be included via a load() form or similar. Then we
could ditch anything Make-ish but not have a massive binary.
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20111111/505c6451/attachment.pgp>;