Re: Compound conditions and foreign status objects hga@xxxxxx (15 Aug 2020 16:32 UTC)
Re: Compound conditions and foreign status objects Marc Nieper-Wißkirchen (15 Aug 2020 16:46 UTC)
Re: Compound conditions and foreign status objects Marc Nieper-Wißkirchen (15 Aug 2020 17:07 UTC)

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

Am Sa., 15. Aug. 2020 um 18:32 Uhr schrieb <xxxxxx@ancell-ent.com>:
>
> > From: Lassi Kortela <xxxxxx@lassi.io>
> > Date: Friday, August 14, 2020 10:43 AM
> >
> > We're working an 'inner property into the next draft for chaining nested
> > errors together.
> >
> > However, R6RS has a standard way to make compound conditions for that
> > purpose. Ideally, on R6RS systems, compound foreign statuses would be
> > represented by compound conditions.
> >
> > <https://api.staging.scheme.org/static/r6rs-lib-errata-corrected.pdf>
> > page 26.
> >
> > [ Not known to exist in other Lisps. ]
>
> I don't see that at all.  I'd rather have SRFI 198 statuses be
> regularized for the benefit of end users and code trying to grok them.
>
> A feature only found in one Scheme standard,

It is the latest standard that actually defines a condition system
with at least some sophistication.

Does anyone know (or has thought about it) whether the R6RS system can
be portably implemented on top of the R7RS primitives?