Custom Query (1030 matches)

Up-to-date linux, amdfam10, clozure 1.9 amd64 and ia32, both behave identically as far as this message is concerned. I don't know CL well, sorry, I'm just busting nil's irritatingly-anything-but-nihilistic chops.

  Welcome to Clozure Common Lisp Version 1.9-r15757  (LinuxX8664)!
  ? (defun nil () t)
  Lisp Breakpoint
  ? for help
  [15021] Clozure CL kernel debugger: 

  Welcome to Clozure Common Lisp Version 1.9-r15757  (LinuxX8664)!
  ? (defun t () nil)
  T
  ? (t)
  NIL

The former seems too harsh and the latter too lenient. Raising exception seems about right, though. This crap shouldn't work either...

  Welcome to Clozure Common Lisp Version 1.9-r15757  (LinuxX8664)!
  ? (setf (symbol-function nil) (lambda () t))
  #<Anonymous Function #x3020006F846F>
  ? (fboundp nil)
  #<Anonymous Function #x3020006F846F>
  ? (nil)
  > Error: NIL is not of type (OR SYMBOL FUNCTION), and can't be FUNCALLed or APPLYed
  > While executing: CCL::TOPLEVEL-EVAL, in process listener(1).
  > Type :POP to abort, :R for a list of available restarts.
  > Type :? for other options.
  1 > (symbolp nil)
  T
  1 > ;eof
  ? (funcall (symbol-function nil))
  T

But it didn't even do the wrong thing right, heh, (nil) raised an error.

This ticket-reporting thing didn't allow me to specify Version 1.9, only some milestone thing.

Regards, Andy Gaynor, euphoria@…

Hey I was throwing an error trying to port an fft library to ccl on my 32 bit linux laptop. The lib is part of a codebase that's possibly proprietary so I can't post it here. Luckily the fix was pretty trivial and 99% sure I found a typo in the ccl source code. See attached svn diff...

(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@…