[Openmcl-devel] compiled closures for Qi?

[Gary Byers]

On Sat, 9 Jun 2007, Michael J. Ferrador wrote:

>
> I've been apropos-ing around CCL:
>
> does anyone know what might be needed for OpenMCL here?
>

How would anyone know what would be needed ?  Is there documentation
anywhere that explains what value *CLOSURES* is supposed to have or
how that value is used ?

Is it supposed to be an exhaustive list of specifiers for all subtypes
of FUNCTION in each supported implementation ? If so, why is it called
*CLOSURES*, and if not, which subtypes of FUNCTION are included and
which are excluded ?



> (DEFUN fix-closures ()
>      #+CMU   (SETQ *closures* '(FUNCTION COMPILED-FUNCTION EVAL::INTERPRETED-FUNCTION))
>      #+CLISP  (SETQ *closures* '(FUNCTION COMPILED-FUNCTION))
>      #+ALLEGRO (SETQ *closures* '(EXCL::CLOSURE FUNCTION COMPILED-FUNCTION))
>      #+SBCL   (SETQ *closures*
>                   '(FUNCTION COMPILED-FUNCTION SB-EVAL:INTERPRETED-FUNCTION))
>     #-(OR CLISP CMU SBCL ALLEGRO)
>       (ERROR "Qi does not recognise this platform ~A" (LISP-IMPLEMENTATION-TYPE)))
>
> I have the other blocks of save (core), & quit
>
> just dabbling on the Prolog side with Qi from http://www.lambdassociates.org/
>

Based on this very small sample size, programming in the 21st century
("c21") may look a lot like it has in ... um, c20 ...

>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>