> 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 purpose
On Tue 22 Apr 2014 18:43, "Diogo F. S. Ramos" writes:
>>> 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.)
>
> Thank you
>> 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.)
Thank you for the reference. `procedure-callees' and
`procedure-callers'
On Sun 20 Apr 2014 20:09, "Diogo F. S. Ramos" 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 `s
