Newsgroups: comp.lang.clos
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!parc.xerox.COM!Gregor
From: Gregor@parc.xerox.COM (Gregor Kiczales)
Subject: (none)
Message-ID: <91Jun27.100333pdt.29186@tracer-bullet.parc.xerox.com>
Sender: Gregor Kiczales <gregor@parc.xerox.com>
Organization: The Ohio State University Department of Computer and Information Science
References: <9106270130.AA13054@kuwait>
Date: Thu, 27 Jun 1991 17:03:21 GMT
Lines: 16

   Date:	Wed, 26 Jun 1991 18:30:15 -0700
   From:	jonl%kuwait@lucid.com (Jon L White)

   re: 5.  Avoid the use of TYPEP.  Replace (typep object 'frog) with
       (frog-p object) where:

   This would be a very implementation-specific piece of advice, *if*
   the issue you are worried about is running speed.  

There are better reasons than running speed to do this.  Doing so is a
small step towards de-unifying implementation inheritance and type
inheritance.  While doing this isn't completely figured out yet, the
recent papers by Snyder, Cook and crowd are persuasive enough to me to
suggest that trying to program this way is a good idea.

Gregor