On 05/02/11 11:19, Andy Wingo wrote:
> On Mon 02 May 2011 11:51, Alaric Snell-Pym <alaric@snell-pym.org.uk> writes:
>
>> (EXCEPTION? foo)
>> (EXCEPTION->STRING foo)
>> ...and for advanced implementations, (EXCEPTION-BACKTRACE foo) etc...
>
> This assumes a mode of debugging after the stack is unwound, instead of
> debugging before throwing the exception.  In the latter case, not only
> do you have the possibility to restart, you don't need to reify anything
> to have access to a backtrace.
>
> I don't think this is the sort of thing that a Scheme report should
> standardize.

Same here. I wasn't suggesting standardising it, merely that for
implementations that have this concept, a way of providing it across
ERROR exceptions and more complex hierarchical exceptions would be nice.

> Andy

--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports