[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Ludovic Courtès
Subject: Re: [Geiser-users] ‘geiser-guile-load-path’ v s. ‘%load-compiled-path’
Date: Fri, 13 Sep 2013 15:24:31 +0200
User-agent: Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux)

ludo-mXXj517/address@hidden (Ludovic Courtès) skribis:

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

Actually yes!  I’ve just been reminded that 2.0.9 gained a -C flag for
that.  However, it’s 2.0.9-and-later, so probably not something you can
use in Geiser.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]