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)

raise-foreign-error Marc Nieper-Wißkirchen 16 Aug 2020 14:30 UTC

Draft #3 contains the following paragraph:

**
raise-foreign-error takes the foreign-error-object returned by
make-foreign-error and raises an exception in a manner suitable for
the Scheme implementation it is running on. Its actions are at the
complete discretion of that Scheme implementation's community. If the
optional argument continuable is not the default of #f, it will
ideally raise a continuable exception.
**

I have three questions concerning this:

(1) What does "in a manner suitable for the Scheme implementation it
is running on" mean?
(2) What does "ideally raise a continuable exception" mean?
(3) Haven't we agreed on that mixing raising continuable and
non-continuable exceptions in one procedure is a bad thing because
"raise" and "raise-continuable" are two very different types of
procedures (the former actually being a continuation)?

Thanks,

Marc