gmane.lisp.cmucl.general

When slots :type are used

Didier Verna — 2008-11-26T17:53:02

Hi again, Section "2.23.2 Slot Type Checking" continues to puzzle me, especially the fact that you have to be within *methods* for the :type slot option to be taken in consideration when writing something to a slot. For instance, with: (defclass foo () ((a :type fixnum))) (defvar *object* (make-instance 'foo)) (setf (slot-value *object* 'a) 3.5) ;; this works like a charm but: (defmethod setslot ((foo foo) val) (setf (slot-value foo 'a) val)) (setslot *object* 3.5) ;; triggers a type error Can somebody provide a rationale for this ?? Thanks.

:type slot option in classes

Didier Verna — 2008-11-26T09:39:47

Hello, Reading section "2.23.2 Slot Type Checking" of the manual, I'm inclined to think that the following code should trigger an error when instanciating the class. But it doesn't: | (declaim (optimize (speed 0) | (compilation-speed 0) | (safety 3) | (debug 0))) | | | (defclass foo () | ((slot :type single-float :initform "bar"))) The behavior is not undefined (as the standard would say), but coherent in the sense that objects of any type can be correctly written and read from the slot, just as if the :type option was not given. Am I missing something ? Thanks! BTW, some more info: * pcl::*use-slot-types-p* T * (lisp-implementation-version) "CVS 19d 19d-release (19D)"

compilation note -> style-warning?

Nicolas Neuss — 2008-11-25T10:11:35

Hello, in the following code a compilation note (returning of double) triggers also a style-warning. Is this intended? (I cannot see how to improve the style...) (catch 'trap (handler-bind ((serious-condition #'(lambda (condition) (throw 'trap condition))) (warning #'(lambda (condition) (throw 'trap condition)))) (compile nil (lambda (x n) (declare (type fixnum n) (type (simple-array double-float (*)) x)) (declare (optimize (safety 0) (space 0) (debug 0) (speed 3))) (loop for i of-type fixnum from 0 below n summing (* (aref x i) (aref x i)) of-type double-float))))) Yours, Nicolas

Please explain this compiler note

Didier Verna — 2008-11-19T15:40:18

[Fwd: ILC]

Raymond Toy — 2008-10-29T13:04:44

In case you didn't already know, there's another Lisp conference coming up. Ray, who might go if he plans things out better this time than he did for OOPSLA.

Mailing list issues?

Raymond Toy — 2008-10-13T13:35:42

Can someone check the mailing lists? It appears that subscriptions work but, in fact, you're not, because messages sent don't make to the list and new messages aren't forwarded to the new subscriber. Well, at least one person has mentioned to me that his subscription doesn't work. Thanks, Ray

CVS down

Raymond Toy — 2008-10-09T13:47:54

Just found out that common-lisp.net is being moved to a new server today (or yesterday). I guess the move is still in progress, so CVS is currently down. Trac is also down. common-lisp.net is up, though. It's being worked on. Ray

SSE2 support

Raymond Toy — 2008-10-06T14:29:52

While you're waiting for the 2008-10 snapshot, here's something new you can play with: SSE2 support for CMUCL. You can grab the (large) binary for Linux from This includes support for both x87 and sse2. (This idea was suggested by Carl.) The C runtime will try to determine if you machine supports sse2 and loads the sse2 core if it does. Otherwise, it loads the x87 core. There's a new command-line switch to allow you to select between the x87 or sse2 core if you want to force a certain core. "-fpu x87" selects the x87 core, and "-fpu sse2" selects the sse2 core. I've run some numerical tests and the sse2 core works just fine. I do not know if the sse2 core is faster or slower than the x87 core, but it does fix some issues with double-float support for x87. (See trac ticket #15, which now ret

Undefined functions bug summary

Steven Edwards — 2008-10-05T17:29:49

When compiling with (speed 3) (safety 0) (space 0), I get: ; Warning: These functions are undefined: ; STREAM::%LISTEN STREAM::%READ-CHAR STREAM::%UNREAD-CHAR STREAM- LISTEN STREAM-READ-CHAR STREAM-UNREAD-CHAR ; because of references to: listen read-char unread-char (some with stream arguments, some without) However, the compiled code works fine. Banner: CMU Common Lisp 19e (19E), running on gail With core: /Users/sje/cmucl-19e-x86-darwin/lib/cmucl/lib/lisp.core Dumped on: Thu, 2008-05-01 20:38:02-04:00 on macmini See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 Compilation banner: ; Python version 1.1, VM version Intel x86 on 05 OCT 08 01:22:45 pm.

Error loading flexi-streams on CMUCL + Debian

Watt Poosanguansit — 2008-09-30T01:40:36

I am new to CMUCL and flexi-streams. I tried to load the library and I got the message below. I have asked this on flexi-streams list and I was told this might be a better place since this might have to do with how CMUCL load the files. Any help is appreciated. ; loading system definition from ; /usr/local/asdf-install/site-systems/flexi-streams.asd into ; # ;; Loading #P"/usr/local/asdf-install/site/flexi-streams-1.0.7/flexi-streams.asd". ; registering # as FLEXI-STREAMS ; registering # as FLEXI-STREAMS-TEST ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. O C): ; Compiling Top-Level Form: ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/packages.x86f". ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/mapping.x86f". Error in function LISP::INTERNAL-LOAD: File has a fasl file type,

Another stumper compilation diagnostic

Steven Edwards — 2008-09-24T18:08:09

The source (most of it, anyway): ;;; Time mark structure (defstruct (timemark (:print-function (lambda (my-timemark my-stream my-level) (declare (ignore my-level)) (encode-timemark my-stream my-timemark)))) (year 0 :type fixnum) ; Year [0-9999] (month 0 :type fixnum) ; Month number [1-12] (date 0 :type fixnum) ; Day of month number [1-31] (hour 0 :type fixnum) ; Hour of day [0-23] (minute 0 :type fixnum) ; Minute of hour [0-59] (second 0 :type fixnum) ; Second of minute [0-59] (msec 0 :type fixnum)) ; Millisecond of second [0-999] ;;; Time mark routines (defun calc-timemark-from-tm-list (my-tm-list) "Return a new time mark calculated from a time mark list." (make-timemark :year (sixth my-tm-list) :month (fifth my-tm-list) :date (fourth my-tm-list) :hour (third my-tm-list) :minute (second my-tm-list) :second (first my-tm-list) :msec 0

Compiling macros with an optional function parameter?

Denis Papathanasiou — 2008-09-24T16:44:49

I'm not sure if this is a Lisp thing or an issue specific to CMUCL, but when I compile this macro and try to include the resulting x86f file into a larger binary (i.e. using 'cat'), I see this: "Error in batch processing: Cannot dump objects of type FUNCTION into fasl files." This is the macro: (defmacro update-list-hash (hash data-key data-value &optional (test-fn #'string-equal)) "Update the given hash (key:value is 1:n) with data by adding data to the list of values for the key." `(let ((current (gethash ,data-key ,hash))) (if (member ,data-value current :test ,test-fn) current (setf (gethash ,data-key ,hash) (cons ,data-value current))))) If I remove the optional parameter and explicitly specify the member :test parameter inside the macro, I can compile and cat the resulting x86f file without any problems. Any idea why this might be happening and what (if any) work-arounds there are? I'm using CMUCL 19e on debian etch.

Another spurious compilation diagnostic?

Steven Edwards — 2008-09-22T21:06:09

Greetings again, list readers: It seems that every time I compile something like: (list-length some-random-list) I get a compiler warning: ; (LIST-LENGTH SOME-RANDOM-LIST) ; --> BLOCK DO BLOCK LET TAGBODY WHEN COND IF PROGN RETURN ; ==> ; (RETURN-FROM NIL NIL) ; Warning: This is not a (VALUES &OPTIONAL REAL &REST T): ; NIL ; ; [Last message occurs 2 times] Any ideas?

Spurious compilation diagnostic?

Steven Edwards — 2008-09-21T07:45:50

Greetings, list readers: Banner: CMU Common Lisp 19e (19E), running on gail With core: /Users/sje/cmucl-19e-x86-darwin/lib/cmucl/lib/lisp.core Dumped on: Thu, 2008-05-01 20:38:02-04:00 on macmini See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 User source (wrapper for read-char): (defun read-ch (my-stream) "Return the next character on an input stream; return nil on end of stream." (read-char my-stream nil nil)) Compilation warning output: ; In: DEFUN READ-CH ; (READ-CHAR MY-STREAM NIL NIL) ; --> BLOCK LET LISP::STREAM-DISPATCH ETYPECASE LET COND IF COND IF COND IF ; --> PROGN LET ; ==> ; (STREAM-READ-CHAR STREAM) ; Warning: Undefined function STREAM-READ-CHAR Is the above a spurious compilation diagnostic? The user function works fine.

Buffered stream output bug report

Steven Edwards — 2008-09-13T13:57:55

Banner: CMU Common Lisp 19e (19E), running on gail With core: /Users/sje/cmucl-19e-x86-darwin/lib/cmucl/lib/lisp.core Dumped on: Thu, 2008-05-01 20:38:02-04:00 on macmini See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 Three related bugs: (defun bug0 (my-stream) (write-char #\1 my-stream) (format my-stream "~D" 2) (write-char #\3 my-stream)) (defun bug1 (my-stream) (write-char #\1 my-stream) (format my-stream "~D" 2) (write-char #\3 my-stream) (finish-output my-stream)) (defun bug2 (my-stream) (write-char #\1 my-stream) (finish-output my-stream) (format my-stream "~D" 2) (finish-output my-stream) (write-char #\3 my-stream) (finish-output my-stream)) (bug0 t) -> should print "123". It doesn't. (bug1 t) -> should print "123". It doesn't. (bug2 t) -> should print "123". It doesn't. In fact, the outputs are all different. GNU clisp seems to handle these okay, as

defmethod+flet

Walter C. Pelissero — 2008-07-21T15:13:59

I just stumbled in something that doesn't look quite right to me. Under 19E the following is legal code: (defmethod foo (x) x) (defmethod bar (x) (flet ((foo (a) (declare (ignore a)))) (foo))) while I'd expect a warning for the missing argument in the call of FOO. On the other hand the following code does produce a warning in the call of FOO2 (missing argument): (defmethod foo2 (x) x) (defmethod bar2 (x) (flet ((foo2 ())) (foo2))) SBCL doesn't show this behaviour.

Bug in snapshot 2008-05 for x86

Raymond Toy (RT/EUS — 2008-05-20T15:36:53

Just discovered a bug in snapshot 2008-05 for all x86 versions. It affects arrays of (unsigned-byte 16) or (signed-byte 16). You can see for yourself with: (defun bar () (declare (optimize (speed 3) (safety 0))) (make-array 8 :element-type '(unsigned-byte 16) :initial-element 42)) Compile this, and (bar) produces #(0 1 2 3 4 5 6 7) instead of #(42 42 42 42 42 42 42 42). The bug may manifest itself in other ways, though, so that when you set an element of such an array, you get some weird number. This will be fixed in the next snapshot. Until then, I would recommend using the previous snapshot. This bug does NOT affect the 19e release. The bug was introduced after the release branch was made. Sorry for the problem, Ray

CMUCL 19e released

Raymond Toy (RT/EUS — 2008-05-19T15:21:34

========================== C M U C L 19 e ============================= The CMUCL project is pleased to announce the release of CMUCL 19e. This is a major release which contains numerous enhancements and bugfixes from the 19d release. CMUCL is a free, high performance implementation of the Common Lisp programming language which runs on most major Unix platforms. It mainly conforms to the ANSI Common Lisp standard. CMUCL provides a sophisticated native code compiler; a powerful foreign function interface; an implementation of CLOS, the Common Lisp Object System, which includes multimethods and a metaobject protocol; a source-level debugger and code profiler; and an Emacs-like editor implemented in Common Lisp. CMUCL is maintained by a team of volunteers collaborating over the Internet, and is mostly in the public domain. New in this release: * Supported system: - Support for Mac OS X/Intel has been added for OSX 10.5 and later. * Issues - One some openSUSE systems, cmucl will fail to

Installing CMUCL on a remote machine

scem geyik — 2008-03-26T19:08:36

Hello, I have a 14-year old software that I am trying to run on a new machine. The author of the software has written that he has tested it with cmucl 17e, but this can not be installed on a solaris 2.10 machine. Due to this I tried to install the closest possible version (18a) to the solaris 2.10 machine which I connect remotely and I don't have the administrator rights. I opened the zip files (solaris24.tgz and solaris24.extra.tgz) to my user directory --I did the necessary environment variable changes-- and set the CMUCLLIB to my user director (which is not /lib)but some_user_directory/lib and when I try to run lisp it says: can not find file: /usr/local/lib/cmucl/lib/lisp.core, it doesn't exisst what should I do for lisp to see lisp.core, I tried lisp -core lisp.core but this time it gave Segmentation Fault. Any help would be appreciated, thanks in advance _________________________________________________________________ Watch Cause Effect, a show about real people making a real differen

cmucl-19e + gcc43 better, not quite there

Rex Dieter — 2008-03-14T19:37:44

Tried out cmucl-19e-pre1, and this works better (than cmucl-19d) and gets further, but fails in some asm in ../../src/lisp/x86-assem.S ../../src/lisp/x86-assem.S: Assembler messages: ../../src/lisp/x86-assem.S:84: Error: suffix or operands invalid for `fnstsw' ?? For complete build.log, see http://koji.fedoraproject.org/koji/getfile?taskID=515618&name=build.log Further, attached is a quick-n-dirty patch I needed to make it not choke on #include -> #include which contains #ifdef __i386__ #include "unistd_32.h" #else #include "unistd_64.h" #endif on recent kernel-headers. In short, translating -I- to use -iquote instead (and have the build respect our rpm optflags)

[Newbie Q] Detecting what packages are defined

David A. Cobb — 2008-02-15T20:03:01

I've read the documentation -- even the Hyperspec, tho' it gives me a headache. I must not have seen the "right" document, because I miss the answer to a simple question: How can I determine what packages are already defined? I see a lot of symbols that look like package-names in *FEATURES*, but nothing to suggest that that is automatic or even recommended. If I look at *MODULES*, the names I see don't look like known packages; and of course *MODULES* is "depreciated." The spec seems to require that the namespace of package-names is unique and separate from any other namespace, so enumerating it shouldn't be such a big deal. TIA