unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: No Itisnt <theseaisinhere@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Lua
Date: Thu, 03 Jun 2010 21:29:15 +0200	[thread overview]
Message-ID: <m3r5knx6d0.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTilOXRUlyKHBe9l8NeDin7vOBhleCllOcUDhZ0QG@mail.gmail.com> (No Itisnt's message of "Thu, 3 Jun 2010 03:32:47 -0500")

Heya,

On Thu 03 Jun 2010 10:32, No Itisnt <theseaisinhere@gmail.com> writes:

> - Right now I've stuffed everything into one file. When it doesn't
> recompile automatically (as in I run it without making changes, after
> a run that autocompiled it) it can't resolve MAKE-APPLICATION from
> (language tree-il) so a bunch of my tests cause errors. Any known bugs
> that would cause that?

Not a known bug, no. Can you make a test case?

http://www.slate.com/id/2081042

> - Will Guile correctly optimize explicit returns as tail calls? I
> couldn't tell from a quick look but my gut feeling is that it only
> optimizes implicit returns, as opposed to those using (primitive-ref
> return)?

No, it will not. The primitive-ref return thing is a hack; the proper
way to do this (I think?) is to use prompts and aborts, and also enhance
Guile's compiler to do source-to-source translation of Tree-IL in which
an intraprocedural abort to a prompt with a fresh tag that cannot escape
the prompt expression does some kind of CPS on the expression to leave
the return expression in tail context.

Otherwise we could add `return' to Tree-IL, but that is nasty I think;
or another hack (nasty, but perhaps expedient). Better to CPS, in the
long run anyway.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-06-03 19:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 18:00 Lua No Itisnt
2010-05-22 21:04 ` Lua Ludovic Courtès
2010-06-03  8:32 ` Lua No Itisnt
2010-06-03 19:29   ` Andy Wingo [this message]
2010-06-03 20:36     ` Lua No Itisnt
2010-06-03 22:04       ` Lua Andy Wingo
2010-06-03 22:07       ` Lua Andy Wingo
2010-06-13 21:03 ` Lua No Itisnt
2010-06-14 20:50   ` Lua Andy Wingo
2010-06-15  2:51     ` Lua No Itisnt

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=m3r5knx6d0.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=theseaisinhere@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).