[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] Move `print-error-message' into (chicken c

From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] Move `print-error-message' into (chicken condition)
Date: Tue, 8 Aug 2017 19:34:10 +0200
User-agent: NeoMutt/20170113 (1.7.2)

On Mon, Aug 07, 2017 at 09:46:19PM +1200, Evan Hanson wrote:
> Per Felix and Peter's recent proposal.
> That post also mentions an "error-message" procedure that should be
> moved, but I'm not sure what that refers to so haven't included it (is
> that possibly a mistake, or maybe something that we decided to add to
> the standard library but haven't gotten to yet?).

Thanks!  I don't remember either.  It might have something to do with
get-call-chain vs print-call-chain, we might've mistakenly thought
that there would be a [get-]error-message since there's also a

We went back and forth on the call-chain stuff and in the end we decided
it belong in (chicken base) because a call chain is always available and
it has nothing to do with exceptions as such: it's just very often that
you want to know the call chain when an exception is raised, but a call
chain can be requested without having an exception.

When we discussed that, the call chain stuff was listed under
(chicken base), but I now noticed that these are already part of
(chicken condition).  I'm not sure it's worth reverting that again...


Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]