From: Andy Wingo <wingo@pobox.com>
To: "Diogo F. S. Ramos" <dfsr@riseup.net>
Cc: guile-user@gnu.org
Subject: Re: Description of `program-sources' and accessors
Date: Tue, 22 Apr 2014 10:27:48 +0200 [thread overview]
Message-ID: <87ppk9n4zf.fsf@pobox.com> (raw)
In-Reply-To: <877g6j50vl.fsf@nebulosa.milkyway> (Diogo F. S. Ramos's message of "Sun, 20 Apr 2014 15:09:18 -0300")
On Sun 20 Apr 2014 20:09, "Diogo F. S. Ramos" <dfsr@riseup.net> writes:
>>> Is there a place which describes the meaning of each of element of
>>> `program-sources' accessors?
>>
> So, what does "sources" mean? For what I can see, each one correspond
> to a line in a definition. I can't also figure out what a `source:addr'
> is, but I'm guessing it's for the VM.
Sources are a way of mapping bytecode offset to source location. The
addr indicates the byte count since the beginning of the function.
The list is sorted, so if you have adjacent S0 and S1 with addresses A0
and A1, the source information from S0 applies in the range [A0, A1).
> I'm using this interface to know where an object has been defined.
What does this mean? (Have you seen the (system xref) facility? It
doesn't do a good job with non-procedures, but perhaps we could change
that.)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2014-04-22 8:27 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 [this message]
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
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=87ppk9n4zf.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=dfsr@riseup.net \
--cc=guile-user@gnu.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).