From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org, Ian Price <ianprice90@googlemail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: exit & dynamic wind
Date: Wed, 30 Mar 2011 23:43:10 +0200 [thread overview]
Message-ID: <m3wrjgz3m9.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3ei5o1ess.fsf@unquote.localdomain> (Andy Wingo's message of "Wed, 30 Mar 2011 23:25:39 +0200")
On Wed 30 Mar 2011 23:25, Andy Wingo <wingo@pobox.com> writes:
> We didn't see this issue before because compiling eval.scm did not cause
> a `throw'. Interesting, no? But since I changed the implementation of
> ensure-writable-dir to one that probably throws, we see this error.
Sorry, forgot to mention something else. ensure-writable-dir caused the
build to see these errors. The patch under consideration -- allowing
the stack to unwind during a throw to `quit' -- also exercised this
case. I didn't understand it at the time, so I reverted and moved on.
But then the ensure-writable-dir thing brought up the issue again, so
thence the fix, so thence the ability to unwind the stack on a throw to
`quit', even before eval.scm is compiled.
This probably still isn't clear; please ask if you have more questions!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-30 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 13:26 exit & dynamic wind Ian Price
2011-03-24 19:23 ` Andy Wingo
2011-03-25 1:52 ` Neil Jerram
2011-03-25 16:45 ` Andy Wingo
2011-03-30 10:45 ` Andy Wingo
2011-03-30 18:31 ` Neil Jerram
2011-03-30 21:25 ` Andy Wingo
2011-03-30 21:43 ` Andy Wingo [this message]
2011-03-30 21:54 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 19:06 Mike Gran
2011-03-30 21:28 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wrjgz3m9.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.com \
--cc=neil@ossau.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).