Re: [Geiser-users] ‘geiser-guile-load-path’ v s. ‘%load-compiled-path’

[Ludovic Courtès]

Howdy!

"Jose A. Ortega Ruiz" <jao-mXXj517/address@hidden> skribis:

> On Mon, Sep 02 2013, Ludovic Courtès wrote:
>
>> Hello,
>>
>> Currently ‘geiser-guile-load-path’ maps to a series of -L flags on the
>> ‘guile’ command line, which augments ‘%load-path’.
>>
>> However, it is usually desirable to augment ‘%load-compiled-path’ in
>> addition to ‘%load-path’.  Failing to do so, Geiser misses an
>> opportunity to use fresh .go files that may be sitting next to the
>> source files; worse, it may end up using stale .go files, which can be a
>> problem when ABI changes are introduced (for instance when the body of
>> macros is changed, as is the case with SRFI-9 record accessors.)
>>
>> What about adding an initialization snippet to augment
>> ‘%load-compiled-path’ accordingly?
>
> Makes sense... is there a flag similar to -L for %load-compiled-path?

No.

> And can we share the directories in geiser-guile-load-path for both
> non-compiled and compiled paths or is it better to have separate lists?

For the purposes of Geiser, I think it’s better to have a single list
(even for Guile itself, it’s not clear to me what having separate lists
buys us.)

> We also have a command to augment %load-path while the REPL is running:
> would it make sense to add also the requested directory to
> %load-compiled-path? (having a separate command sound a bit too much,
> but is doable if that's the right thing to do...)

What do you mean by “while the REPL is running”?  Anyway, both variables
should be augmented similarly, I think.

Thanks!

Ludo’.