From: Roger Kehr
Subject: CMUCL: defclass and defgeneric
Date: Mon, 21 Jul 1997 00:00:00 +0000
Message-ID: <5qv72s$mr$1@news.th-darmstadt.de>

	Hello out there,

I frequently program in CLOS and I had a look at CMUCL.

CMUCL always tells me at the end of a compilation that it does not
know anything about the defined classes and methods.

What is the right way to inform CMUCL that classes defined via
defclass are types, and that generic functions are functions ?

BTW: Allegro CL and CLISP do not have any problems with that.

I suspect that a certain kind of eval-when is necesary...

Any hints are welcome.


Best regards,

Roger

-- 
======================================================================
Roger Kehr			   ····@iti.informatik.th-darmstadt.de
Computer Science Department          Technical University of Darmstadt

From: Mark McConnell
Subject: Re: CMUCL: defclass and defgeneric
Date: Tue, 22 Jul 1997 00:00:00 +0000
Message-ID: <33D53902.79D8@math.okstate.edu>

Roger Kehr wrote:

> CMUCL always tells me at the end of a compilation that it does not
> know anything about the defined classes and methods.
> 
> What is the right way to inform CMUCL that classes defined via
> defclass are types, and that generic functions are functions ?

In my experience, you don't have to.  The compiler issues the warnings
sometime during the middle of the compilation process, but, by the
time the code is loaded, it knows all about your classes and
methods.  A CMUCL guru could explain more precisely.

Here is a quick fix: first load your code in interpreted mode

   (load "foo.lisp")

and _then_ compile it

   (compile-file "foo" :error-output nil :error-file t :load t)

[Then look at the file cow.err]