raise-foreign-error Marc Nieper-Wißkirchen (16 Aug 2020 14:30 UTC)
Re: raise-foreign-error hga@xxxxxx (16 Aug 2020 15:04 UTC)
Re: raise-foreign-error Marc Nieper-Wißkirchen (16 Aug 2020 15:26 UTC)
Re: raise-foreign-error hga@xxxxxx (16 Aug 2020 16:02 UTC)
Re: raise-foreign-error John Cowan (17 Aug 2020 02:35 UTC)
Re: raise-foreign-error hga@xxxxxx (17 Aug 2020 11:58 UTC)
Re: raise-foreign-error Lassi Kortela (17 Aug 2020 12:06 UTC)
Re: raise-foreign-error hga@xxxxxx (17 Aug 2020 14:20 UTC)
R6RS condition type hierarchy Lassi Kortela (17 Aug 2020 12:10 UTC)
Re: R6RS condition type hierarchy John Cowan (17 Aug 2020 13:40 UTC)
Re: R6RS condition type hierarchy Lassi Kortela (17 Aug 2020 14:47 UTC)
Re: R6RS condition type hierarchy Marc Nieper-Wißkirchen (17 Aug 2020 14:56 UTC)

R6RS condition type hierarchy Lassi Kortela 17 Aug 2020 12:10 UTC

> It's identical to R7RS, fortunately; the exception is that the object
> you raise must be of type &condition (and preferably of subtype &error
> if it will always be raised non-continuably).  Not all R6RS systems
> enforce this requirement.

We could just specify that R6RS systems add a &foreign condition type.

However, the situation is complicated by the fact that not all foreign
statuses are errors. Hence it would be misleading to make &foreign a
subtype or &error. We could make it a subtype of &conditon as you
suggest, but then foreign errors are not a subtype of &error. If a R6RS
wizard is lurking, advice would be helpful.

Anyway, this doesn't need to be in the next draft.