unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
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: Sat, 19 Apr 2014 13:43:55 +0200	[thread overview]
Message-ID: <87bnvxo878.fsf@pobox.com> (raw)
In-Reply-To: <87oazx4oqd.fsf@nebulosa.milkyway> (Diogo F. S. Ramos's message of "Sat, 19 Apr 2014 07:07:06 -0300")

Hi,

On Sat 19 Apr 2014 12:07, "Diogo F. S. Ramos" <dfsr@riseup.net> writes:

> Is there a place which describes the meaning of each of element of
> `program-sources' accessors?
>
> For example:
>
>   (source:addr (program-sources every)) => (0 "srfi/srfi-1.scm" 810 . 0)
>
> What does each element of the improper list mean?
>
> Also for `source:file', `source:line' and `source:column'.  The first
> two are also improper lists, but the last is a list of improper lists.

Note that this is an interface that is very specific to Guile 2.0's
VM, and it's gnarly in many ways.  However :)  What program-sources
returns is a list of sources.  Therefore source:addr should be called on
the elements of program-sources, not on the list as a whole.

Unfortunately sources are represented in this interface as improper
lists -- source:addr is just car.  So it works on the list as a whole;
hence the confusion.  Perhaps now that this confusion is resolved, the
text in the manual will make more sense.

Regards,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2014-04-19 11:43 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 [this message]
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

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=87bnvxo878.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).