guile-devel
[Top][All Lists]
Advanced

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

Re: enhancement requests


From: Wolfgang J Moeller
Subject: Re: enhancement requests
Date: Mon, 18 Apr 2011 11:53:26 +0200 (CEST)

On Fri, 15 Apr 2011, Andy Wingo wrote:

> Hi Wolfgang,
>
> On Mon 21 Mar 2011 01:24, Wolfgang J Moeller <address@hidden> 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.

There are already 2 "operational modes": Default, and --no-auto-compile.
I'm indeed asking for a "load-ignoring-cached-go" from _within_ both of these 
modes,
not for a third mode that makes for even more variation in what ought to be 
tested.

Something like INCLUDE (which however, doesn't work quite the same as LOAD -
cf. my "prelude" example) would be fine ... there's no point in [file-]compiling
test programs for [in particular] macros.

Of course, currently I do have an emacs dired window open into the .cache 
directory
in order to check for (and delete) compiler output.
Didn't you claim that I should not need to do so?

Best regards,

Wolfgang J. Moeller, Tel. +49 551 47361, wjm<AT>heenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+-------- http://www.heenes.com/



reply via email to

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