Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!caen!malgudi!ucunix.san.uc.edu!tut.cis.ohio-state.edu!cis.ohio-state.edu!lucid.COM!jonl%kuwait
From: jonl%kuwait@lucid.COM (Jon L White)
Newsgroups: comp.lang.clos
Subject: Printer methods for conditions
Message-ID: <9106280608.AA14759@kuwait>
Date: 28 Jun 91 06:08:00 GMT
References: <286AA5DC.7B4@deneva.sdd.trw.com>
Sender: daemon@cis.ohio-state.edu
Organization: The Ohio State University Department of Computer and Information Science
Lines: 24

re: An even worse exacerbation of my problem is that the latest version of
    Lucid Lisp that I am using still represents conditions as defstructs
    so there isn't even a printer method for conditions since they aren't
    classes. I would like to hear comments on what solution the X3J13
    committee has decided on for the standard.

When you load in the CLOS submodule, the "defstructs" automagically
become classes (but of metaclass Structure-Class of course.)  You 
*can* define PRINT-OJBECT methods on these.

Probably a more limiting "feature" of Lucid's 4.0 release is that the 
condition system implemented is "Pitman version 18" rather than the 
emmended X3J13 proposal worked out during the past two years.  The 
differences can be annoyiing, but probably not crippling (I'm aware 
that CLIM for example has some specific workarounds for the differences.)

Somehow, the name Kim Barrett comes to mind when I think of someone
who might be able and wiling to give a summary of these differences, 
and how they would affect your usage.  Try asking kab@chestnut.com, 
if he isn't reading and replying to this list [but please, don't 
everybody start sending mail to him if he doesn't reply publicly.]


-- JonL --