[Top][All Lists]

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

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

From: Ludovic Courtès
Subject: [Geiser-users] ‘geiser-guile-load-path’ v s. ‘%load-compiled-path’
Date: Mon, 02 Sep 2013 22:07:39 +0200
User-agent: Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux)


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?


reply via email to

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