Re: [Matlisp-users] Re: Problems compiling latest CVS version

[Raymond T. <to...@rt...>]

>>>>> "Nicolas" =3D=3D Nicolas Neuss <Nic...@iw...> =
writes:

    Nicolas> wb...@gm... (Wolfhard Bu=DF) writes:
    >> Replacing the line
    >>=20
    >> (setf (find-class 'real) (find-class 'cl:real))
    >>=20
    >> in packages.lisp with:
    >>=20
    >> #+:cmu (setf (pcl:find-class 'real) (pcl:find-class 'cl:real))
    >> #+:allegro (setf (find-class 'real) (find-class 'cl:real))
    >>=20
    >> works for me.
    >>=20
    >> Cheers.

    Nicolas> Thanks, Wolfhard.

I've applied Wolfhard's fix so older versions of CMUCL will still
work.

    Nicolas> This more or less works.  But I get still a conflict for REAL =
when I want
    Nicolas> to use both COMMON-LISP and MATLISP in some package.  There sh=
ould be some
    Nicolas> cleaner remedy.

Shouldn't USE'ing MATLISP in some other package be enough since
MATLISP use's COMMON-LISP?  (I can never remember these package issues
because I don't do it very often.)

    Nicolas> I have no time for the next weeks to examine further.  Thus I =
went back to
    Nicolas> my stable environment with old CMUCL and old Matlisp.  But lat=
er this year,
    Nicolas> I will surely be interested in the new Matlisp.  I think that =
Ray's
    Nicolas> splitting of matrix-ref, for example, is in the right directio=
n for
    Nicolas> improving performance.

If you get a chance, I hope you'll try it again with current CMUCL and
current Matlisp.  I'd appreciate any feedback you might have.

Ray