From: "Diogo F. S. Ramos" <dfsr@riseup.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: Description of `program-sources' and accessors
Date: Tue, 22 Apr 2014 19:09:42 -0300 [thread overview]
Message-ID: <87mwfddnix.fsf@nebulosa.milkyway> (raw)
In-Reply-To: <87d2g9ma8o.fsf@pobox.com> (Andy Wingo's message of "Tue, 22 Apr 2014 21:31:51 +0200")
> On the other hand it is probably possible to know where a name "foo" in
> a module (bar) is defined, through VM internals. Not currently
> implemented. But that's a mapping from fully-qualified _names_ to
> locations, not values to locations.
I didn't think of this distinction. For my purposes, the
fully-qualified name is indeed what I want, not the value.
Oh well.
prev parent reply other threads:[~2014-04-22 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 10:07 Description of `program-sources' and accessors Diogo F. S. Ramos
2014-04-19 11:43 ` Andy Wingo
2014-04-20 18:09 ` Diogo F. S. Ramos
2014-04-22 8:27 ` Andy Wingo
2014-04-22 16:43 ` Diogo F. S. Ramos
2014-04-22 19:31 ` Andy Wingo
2014-04-22 22:09 ` Diogo F. S. Ramos [this message]
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=87mwfddnix.fsf@nebulosa.milkyway \
--to=dfsr@riseup.net \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.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).