From: Marko Rauhamaa <marko@pacujo.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: Guile 2.0 interpretation vs compilation
Date: Mon, 06 Oct 2014 09:33:55 +0300 [thread overview]
Message-ID: <87wq8d671o.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <87d2a5esk0.fsf@netris.org> (Mark H. Weaver's message of "Mon, 06 Oct 2014 00:22:07 -0400")
Mark H Weaver <mhw@netris.org>:
> This is expected but not ideal. Our primitive evaluator does not
> preserve non-toplevel variable names, and therefore the associated
> procedure names are lost. Maybe we can fix this in Guile 2.2.
I noticed the issue because I have software that depends on the
procedure-name of inner functions. I can live with this guile-2.0 quirk
if it is considered a guile defect. However, if the semantics of
procedure-name of inner functions is unspecified, I'll have to look at
refactoring my code.
Marko
next prev parent reply other threads:[~2014-10-06 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 11:03 Guile 2.0 interpretation vs compilation Marko Rauhamaa
2014-10-06 4:22 ` Mark H Weaver
2014-10-06 6:33 ` Marko Rauhamaa [this message]
2014-10-06 6:52 ` Mark H Weaver
2014-10-06 7:58 ` Mark H Weaver
2014-10-06 19:05 ` Marko Rauhamaa
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=87wq8d671o.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
/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).