From: Andy Wingo <wingo@pobox.com>
To: Jon Herron <jon.herron@yahoo.com>
Cc: guile-devel@gnu.org
Subject: Re: (language tree-il compile-glil) question
Date: Tue, 27 Apr 2010 23:06:39 +0200 [thread overview]
Message-ID: <m37hns61wg.fsf@pobox.com> (raw)
In-Reply-To: <332120.3801.qm@web112308.mail.gq1.yahoo.com> (Jon Herron's message of "Mon, 26 Apr 2010 22:40:15 -0700 (PDT)")
On Tue 27 Apr 2010 07:40, Jon Herron <jon.herron@yahoo.com> writes:
> In some late night hacking this evening/morn I came across a question
> in (language tree-il compile-glil) - should line 126 read ((return . 1)
> . return) instead of ((return . 1) return)?
Indeed, it appears that way. I have fixed and pushed, thanks for the
note!
Return is a hack, though; I would rather express returns using prompt
and abort, with some tree-il inliner logic to simplify some cases. But I
was in a rush, so return is how it is.
I'll be updating tree-il and vm docs to correspond to reality this
weekend.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-04-27 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:40 (language tree-il compile-glil) question Jon Herron
2010-04-27 21:06 ` Andy Wingo [this message]
2010-04-27 22:09 ` Jon Herron
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=m37hns61wg.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jon.herron@yahoo.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).