|
From: Raymond T. <to...@rt...> - 2003-10-13 13:58:45
|
>>>>> "Nicolas" == Nicolas Neuss <Nic...@iw...> writes:
Nicolas> I encounter the following problems with Matlisp:
Nicolas> 1. With the snapshot cmucl-2003-10-x86-linux.tar.bz2, I get the following
[snip]
Nicolas> Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
Nicolas> #() is not of type (OR CONS
Nicolas> BASE-STRING
Nicolas> LISP::PATTERN
Nicolas> (MEMBER NIL :UNSPECIFIC :WILD))
Nicolas> [Condition of type TYPE-ERROR]
I think this is fixed in CVS now.
Nicolas> 2. This works with cmucl-2003-09-14-x86-linux.tar.bz2. I still get a
Nicolas> conflict when loading the following package definition:
Nicolas> (defpackage "ALGEBRA"
Nicolas> (:use "COMMON-LISP" "GENERAL" "MACROS" "UTILITIES" "MATLISP")
Nicolas> (:import-from "EXTENSIONS" "REQUIRED-ARGUMENT")
Nicolas> (:export
Nicolas> ...))
Nicolas> Namely:
Nicolas> ---------------------------------------------------------------------------
Nicolas> Error in function USE-PACKAGE:
Nicolas> Use'ing package COMMON-LISP results in name conflicts for these symbols:
Nicolas> (MATLISP:REAL MATLISP:REAL)
Nicolas> [Condition of type SIMPLE-ERROR]
Obviously this is because matlisp defines a REAL function that
conflicts with the COMMON-LISP version. Matlisp does a
shadowing-import (I think) to get this to work. You may have to do
the samething in your ALGEBRA package to select the right one. Of
course, then you'll have to use a package qualifier to get REAL from
the other package.
Nicolas> Yes, "ref.lisp" looks a little messy now. Did it help in performance? I
Found and fixed one a couple of silly typo bugs this weekend.
When I last tested it using JOIN as the test function and enabling
Gerd's PCL changes (included in recent CMUCL snapshots), it did help.
The gain wasn't huge though---maybe a few percent?
Nicolas> think that the separation in 1d and 2d access is right, at least it fitted
Nicolas> well with my extensions.
That's good. So the changes, even if they don't help with speed, is
helping you!
Nicolas> I'm looking forward to that snapshot...
Soon. Hopefully before the end of the week.
Ray
|