Custom Query (1030 matches)

What I was trying to do is to declare a function inline. That function has a macro inside. Depending on whether I declaim it inline or notinline I get two different outcomes.

Well I assume that we always should get the same outcome (semantically) independent of whether we declaim something inline or notinline.

Here's a demo:

(in-package :cl-user)

(defpackage :test
  (:use :cl))

(in-package :test)

(defmacro foo ()
  `(funcall ',(intern "FOOBAR")))

(defun foobar ()
  42)

(declaim (inline bar))
(defun bar ()
  (foo))

(in-package :cl-user)

(defun busted ()
  (test::bar))

;; Just for information...
(find-symbol "FOOBAR")			; => FOOBAR, :INTERNAL

;; Error!
(busted)

;;; Lets try it with bar not being inlined.
;;; =======================================

(in-package :test)

(declaim (notinline bar))
(defun bar ()
  (foo))

(in-package :cl-user)

(unintern 'foobar)			; GC that

(defun busted ()
  (test::bar))

;; Runs fine this time.
(busted)

;; Just for information...
(find-symbol "FOOBAR")			; => NIL, NIL

(defun f (n) (if (> n 0) (1+ (f (1- n))) 0))

In GCL,

(handler-case (f 100000)(error (x)(format t "~% handler-case caught error ~s" x) 'boohoo))

results in this:

handler-case caught error #<CONDITIONS::INTERNAL-SIMPLE-STREAM-ERROR.0>

BOOHOO

In Allegro CL, it results in this:

handler-case caught error #<synchronous-operating-system-signal @ #x221524ca>

boohoo

but in CCL we get this...

(handler-case (f 100000)(error (x)(format t "~% handler-case caught error ~s" x) 'boohoo))

Error: Stack overflow on value stack. While executing: F, in process listener(1). Type :POP to abort, :R for a list of available restarts. Type :? for other options

So CCL does not have error handling for this kind of error. If it is to be used seriously as a replacement for GCL on Windows, it has to recover better than this.

version: Welcome to Clozure Common Lisp Version 1.6-r14468M (WindowsX8632)!

Thanks

Richard Fateman fateman@…

Consider the following:

(format nil "~<{~;~{~,3f~^, ~:_~}~;};~:>"
        (list (loop for x from 0 to 30 collecting (expt 1.065 x))))

Under sbcl and LW this puts 11 or 10 (respectively) numbers per line. On CCL (1.7-dev-r14672M-trunk) it does not, returning everything on a single line.

This is a pretty esoteric format string, and it's possible I'm completely misunderstanding what it should do, but I *think* CCL is doing something wrong.