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

[Tobias C. Rittweiler]

Juan Jose Garcia-Ripoll <juanjose.garciaripoll at googlemail.com> writes:

> 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.

Is ECLSRCDIR looked at in a toplevel form in config.lsp; Is that
toplevel form executed only during build, or also during boot of ECL?

The former case does not make sense to me, so I assume it's the
latter. However, in that case, the following seems to indicate that the
locations in annotations do not go over the SRC host if I'm not
mistaken:

tcr at thaleron:~/src/from-upstream/ecl$ ECLSRCDIR=/foo/ ecl-git
;;; Loading #P"/home/tcr/software/ecl-git/lib/ecl-10.3.1/asdf.fas"
;;; Loading #P"/home/tcr/software/ecl-git/lib/ecl-10.3.1/cmp.fas"
;;; Loading #P"/home/tcr/software/ecl-git/lib/ecl-10.3.1/sysfun.lsp"
ECL (Embeddable Common-Lisp) 10.3.1
Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya
Copyright (C) 1993 Giuseppe Attardi
Copyright (C) 2000 Juan J. Garcia-Ripoll
ECL is free software, and you are welcome to redistribute it
under certain conditions; see file 'Copyright' for details.
Type :h for Help.  
Top level in: #<process SI:TOP-LEVEL 092e4fc0>.
> (ext:get-annotation 'si::decode-ihs-env 'si::location :all)

(((DEFUN SI::DECODE-IHS-ENV) #P"/src/tcr/from-upstream/ecl/src/lsp/top.lsp"
  . 31487))


> > 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.

So annotations are a supplemental ressource? I.e. that
EXPAND-SET-DOCUMENTATION does not have a :location annotation does not
constitute case of lost documentation because it does have a file
location via COMPILED-FUNCTION-FILE?

  -T.

-- 
Diese Nachricht wurde auf Viren und andere gefaerliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
Freebits E-Mail Virus Scanner