Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!STONY-BROOK.SCRC.SYMBOLICS.COM!Cassels
From: Cassels@STONY-BROOK.SCRC.SYMBOLICS.COM (Robert A. Cassels)
Newsgroups: comp.sys.ti.explorer
Subject: FLAVORS -> CLOS
Message-ID: <19891017140433.1.CASSELS@TOMATO.SCRC.Symbolics.COM>
Date: 17 Oct 89 14:04:00 GMT
References: <19891017004625.6.SLN@SKAGIT.atc.boeing.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 21


    Date: Mon, 16 Oct 89 17:46 PDT
    From: Stephen Nicoud <snicoud@atc.boeing.com>

    Now that most Lisp vendors will soon be releasing their own versions of
    CLOS, we will be faced with the task of converting our current systems
    (using Flavors) to CLOS.  We've identified several items which will need
    attention, but we're looking for any additional issues which we have not
    addressed.

    My question is, what advice can you give us about moving code from
    FLAVORS (on Symbolics, Explorer, and Sun/Lucid) to CLOS?  What are the
    "gotchas" we need to look out for?  What are the neat tricks to
    converting?  What's the appropriate implemenation "style" to maintain?

The document "Getting Ready for CLOS" is a good place to start.  Copies
are available through your local Symbolics sales office.

    Thanks for your ideas,

    Steve Nicoud	<snicoud@atc.boeing.com>