>>>>> "Nicolas" == Nicolas Neuss <Nicolas.Neuss@iwr.uni-heidelberg.de> writes:
Nicolas> Raymond Toy <toy@rtp.ericsson.se> writes:
>> >>>>> "Stavros" == Stavros Macrakis <stavros.macrakis@verizon.net> writes:
>> Matlisp currently makes a few assumptions about the underlying Lisp:
>>
>> 1. A foreign function interface.
>> 2. The Lisp stores (simple-array double-float (*)) as consecutive
>> double-float numbers, just like C or Fortran would do.
>> 3. There is some way to get at this actual storage address
>> 4. Some way to disable GC when computing the addresses and calling an
>> LAPACK routine
>> 5. CLOS.
Nicolas> These seem to me quite reasonable requirements. Which CL implementations
Nicolas> do not satisfy them? CLISP probably. What about GCL?
Not really sure, but if you don't mind copy-in/copy-out which
eliminates requirements 2-4, then I think just about every Lisp
satisfies the requirements. And maxima doesn't need the CLOS parts of
matlisp, so I think all that's needed is a volunteer. :-)
Ray