Re: enhancement requests

[Andy Wingo <wingo@pobox.com>]

Hi Wolfgang,

On Mon 18 Apr 2011 11:53, Wolfgang J Moeller <wjm@heenes.com> writes:

> On Fri, 15 Apr 2011, Andy Wingo wrote:
>
>> On Mon 21 Mar 2011 01:24, Wolfgang J Moeller <wjm@heenes.com> writes:
>>
>> >> > (4) compiler: Now that compiling into hidden ~.cache/... directories
>> >> >     has been declared the default behaviour, please cater to those
>> >> >     (like me) who'd always look for their compiled files in the
>> >> >     source directory, by providing a command line switch ...
>> >> >     (E.g. "psyntax" provides a useful "include" macro, the use
>> >> >     of which breaks the "need only recompile when source changed"
>> >> >     assumption. Don't like to "make clean" in that hidden place).
>> >>
>> > I'm mostly concerned with interactive use of (un-adorned) "guile" command.
>> > I have files that use macros defined elsewhere - once I have LOADed
>> > (and automatically compiled) such files, and change the macros, there's
>> > [apparently] no way to make guile re-load the source, short of deleting
>> > the (.cache-d) compiler output. Having to locate that in a far-away place
>> > is no fun ... so maybe, what I really want is "load-ignoring-cached-go" ?
>>
>> I have added a --fresh-auto-compile argument to Guile, or equivalently
>> GUILE_AUTO_COMPILE=fresh.  Hopefully that should hack around Guile's
>> missing dependency tracker for the time being.
>
> Sorry, that's not what I intended.

I realize that it's not what you originally asked for.  However I don't
currently know how to support .go alongside .scm files, if you don't
explicitly compile them yourself and set GUILE_LOAD_COMPILED_PATH.

My point was that there shouldn't be a difference between auto-compiling
and not; auto-compilation should work.  It doesn't in this case, because
of lack of dependency tracking, so I added this flag to forceably treat
the cache as stale.

You could also try setting XDG_CACHE_HOME to something in your build
tree...

Andy
-- 
http://wingolog.org/