From: "Jose A. Ortega Ruiz" <jao-mXXj517/zsQ@public.gmane.org>
To: Andy Wingo <wingo-wEGTBA9jqPzQT0dZR+AlfA@public.gmane.org>
Cc: guix-devel-mXXj517/zsQ@public.gmane.org,
geiser-users-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: geiser-xref-callers does not seem to work
Date: Mon, 29 Jan 2018 18:52:12 +0100 [thread overview]
Message-ID: <87d11sblir.fsf@imladris> (raw)
In-Reply-To: <87mv0x59n3.fsf-wEGTBA9jqPzQT0dZR+AlfA@public.gmane.org> (Andy Wingo's message of "Mon, 29 Jan 2018 09:53:04 +0100")
On Mon, Jan 29 2018, Andy Wingo wrote:
> Hi!
>
> Great to hear from you jao :)
likewise :)
> On Sat 27 Jan 2018 17:41, "Jose A. Ortega Ruiz" <jao-mXXj517/zsQ@public.gmane.org> writes:
>
>> hmmm, i was investigating this. the cause geiser fails is that, in the
>> process of looking for other things, it's not able to find
>> `program-arities', exported by (system vm program). i am not sure why:
>
> Weird. Apologies for this, the function just doesn't exist. While
> program-arity exists and calls it, program-arity itself isn't called. I
> think this is detritus of refactoring :(
>
> The facility that Guile uses now for arities is find-program-arity from
> (system vm debug). It takes an address as an argument. Pass
> (program-code prog) if you know you have a program. The issue is that
> with Guile 2.2 there is code that doesn't necessarily have a
> corresponding program object. For example a function defined in a local
> context whose callers can be enumerated by the compiler can be called by
> label instead of by value, and in that case the "closure" of the
> function can be specialized to be e.g. a vector instead of a closure
> object. So while you always have an address, you don't always have a
> program object.
makes sense, i think i can work from there.
> Relatedly, you ask about program-module. This one is sadly no longer
> available. I suspect it is not coming back either :/ I think you have
> to fall back on mapping procedures to files, and files to modules.
i've figured out how to find the filename for a procedure, but i'm
missing what is probably the easier part: give the latter, how do i get
hold of the module object?
> You might find a look to (system vm debug) to be useful for Geiser
> purposes. Note also that the interface to local variables and stack
> frames changed slightly too; see (system vm frame).
yes, i'm reviewing all this. i suspect some other geiser functionality
might have been affected by all this. thanks for the update!
cheers,
jao
--
A ship in port is safe; but that is not what ships are built
for. -Grace Hopper (1906-1992)
next prev parent reply other threads:[~2018-01-29 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 7:55 geiser-xref-callers does not seem to work Chris Marusich
2017-12-16 8:38 ` Chris Marusich
[not found] ` <87y3m3hxts.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-16 18:45 ` Jose A. Ortega Ruiz
2017-12-18 9:34 ` Andy Wingo
2017-12-19 7:47 ` Chris Marusich
[not found] ` <87shc8qt0p.fsf-wEGTBA9jqPzQT0dZR+AlfA@public.gmane.org>
2018-01-27 16:41 ` Jose A. Ortega Ruiz
2018-01-29 8:53 ` Andy Wingo
[not found] ` <87mv0x59n3.fsf-wEGTBA9jqPzQT0dZR+AlfA@public.gmane.org>
2018-01-29 17:52 ` Jose A. Ortega Ruiz [this message]
2018-01-30 8:09 ` Andy Wingo
2018-01-30 22:55 ` [Geiser-users] " Jose A. Ortega Ruiz
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d11sblir.fsf@imladris \
--to=jao-mxxj517/zsq@public.gmane.org \
--cc=geiser-users-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
--cc=guix-devel-mXXj517/zsQ@public.gmane.org \
--cc=wingo-wEGTBA9jqPzQT0dZR+AlfA@public.gmane.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).