Compound conditions and foreign status objects Lassi Kortela (14 Aug 2020 15:43 UTC)
Re: Compound conditions and foreign status objects John Cowan (14 Aug 2020 22:18 UTC)
Re: Compound conditions and foreign status objects Shiro Kawai (14 Aug 2020 23:28 UTC)
Re: Compound conditions and foreign status objects John Cowan (15 Aug 2020 16:45 UTC)
Re: Compound conditions and foreign status objects Marc Nieper-Wißkirchen (15 Aug 2020 16:49 UTC)
Re: Compound conditions and foreign status objects Marc Nieper-Wißkirchen (15 Aug 2020 11:21 UTC)

Re: Compound conditions and foreign status objects Marc Nieper-Wißkirchen 15 Aug 2020 11:20 UTC

Am Sa., 15. Aug. 2020 um 00:18 Uhr schrieb John Cowan <xxxxxx@ccil.org>:
>
> Compound conditions exist in R6RS because it does not have general multiple inheritance, which is what CL uses to give a condition object more than one type simultaneously.  It's pretty much a hack, but then again multiple inheritance is a nightmare.  Note that in R6RS simple conditions are record types, whereas in CL they may or may not be.

Can't we build on the R6RS condition system to make interoperability
easier before inventing something new? (Guile attempts to support both
R6RS and R7RS and a fast R7RS implementation built on top of the R6RS
implementation Chez like Racket on top of Chez would make perfect
sense.)

Marc