[Ecls-list] COMPILED-FUNCTION-FILE returning logical-pathname namestrings

Juan Jose Garcia-Ripoll juanjose.garciaripoll at googlemail.com
Wed Mar 10 09:03:58 UTC 2010


On Wed, Mar 10, 2010 at 9:29 AM, Tobias C. Rittweiler <tcr at freebits.de>wrote:

> Juan Jose Garcia-Ripoll
> <juanjose.garciaripoll at googlemail.com> writes:
>
> > The compiled file names are logical pathnames because this way we can
> move
> > the sources around. Otherwise what is the point that the SRC: hostname is
> > configurable with an environment variable?
>
> Yeah makes sense. Notice that locations-via-annotations do not seem to
> go over SRC:.
>

SRC: will only be used for ECL's sources, but did you find an example in the
core which does not produce a logical pathname? I would like to know.


> Also SI::EXPAND-SET-DOCUMENTATION does not have any annotations.
>

Documentation is most of the time stored in the core (generic functions,
etc), except in those cases that are stored as annotations. Again, an
example of "lost" documentation would be needed.


> I remember that you said in a private mail that COMPILED-FUNCTION-FILE
> should be tried before annotations; why that?
>

It is a cheap check and for compiled functions the source file is normally
stored in the object file, not as an annotation.

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20100310/f29715c4/attachment.html>


More information about the ecl-devel mailing list