From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: "Taylan Ulrich B." <taylanbayirli@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
Dmitry Bogatov <KAction@gnu.org>
Subject: Re: Syntax-rules generate symbol
Date: Tue, 10 Sep 2013 08:11:09 +0200 [thread overview]
Message-ID: <CAMFYt2Zc8gSGyUhvjS404qFB0Xwhe=7OB_Hv-te9wFbXWi1VfA@mail.gmail.com> (raw)
In-Reply-To: <871u4xdaow.fsf@taylan.uni.cx>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
2013/9/9 Taylan Ulrich B. <taylanbayirli@gmail.com>
>
> For anyone who didn't know, "breaking" to arbitrary places is made
> simple (and efficient) with `let/ec' from the module (ice-9 control), a
> wrapper around `call-with-escape-continuation':
>
[...]
I assume that the main reason for using this is efficiency (rather
than simplicity), because allegedly guile's continuations are rather
inefficient.
On one hand, it's good to know that (and would be even better
to be able to find it out by skimming section 6.13 of the manual),
but on the other it would be nicer if the compiler could trace the
usages of continuations and figure out whether a given one is
ever being re-entered, and optimize accordingly.
[-- Attachment #2: Type: text/html, Size: 1206 bytes --]
next prev parent reply other threads:[~2013-09-10 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 16:19 Syntax-rules generate symbol Dmitry Bogatov
2013-09-09 16:59 ` Panicz Maciej Godek
2013-09-09 20:03 ` Taylan Ulrich B.
2013-09-10 6:11 ` Panicz Maciej Godek [this message]
2013-09-10 9:16 ` Taylan Ulrich B.
2013-09-10 10:38 ` Ian Price
2013-09-10 10:33 ` Ian Price
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='CAMFYt2Zc8gSGyUhvjS404qFB0Xwhe=7OB_Hv-te9wFbXWi1VfA@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=KAction@gnu.org \
--cc=guile-user@gnu.org \
--cc=taylanbayirli@gmail.com \
/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).