l...@gnu.org (Ludovic Courtès) writes:
>> It's all running code of one kind or another; is there really a clear
>> distinction here?
>
> Yes: running code in the process being debugged is intrusive, and it
> interferes with the behavior one is trying to observe. It's also
> impossible in many cas
Julian Graham writes:
> Hi Guilers,
>
> With the 1.9 series launched, I wanted to start thinking about R6RS
> libraries again, since it would be awesome to have some semblance of
> an implementation ready by October.
Indeed, yes.
I assume the objective here is to allow a Guile program or module
Hi Neil,
> I assume the objective here is to allow a Guile program or module to
> use a portable R6RS library; i.e., specifically, allowing
> `(use-modules ...)' or `#:use-module (...)' to resolve to an R6RS
> library. Is that correct?
Actually, my immediate-term goal was to add versioning info
Hi szgyg,
On Sat 27 Jun 2009 15:36, szgyg writes:
> Andy Wingo wrote:
>> On Thu 18 Jun 2009 09:33, szgyg writes:
>>> make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build/module'
>>> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
>>> "ice-9/psyntax-pp.go" "../../mod
Hi Julian,
On Sun 28 Jun 2009 02:20, Julian Graham writes:
> With the 1.9 series launched, I wanted to start thinking about R6RS
> libraries again, since it would be awesome to have some semblance of
> an implementation ready by October.
Yes!
>> I think such issues should lead us to have a `:v
Hello,
The attached patch is an attempt to add unused variable reporting to the
compiler, at the GLIL->assembly step. It was quite simple to implement
here, and it should work with all front-ends (Scheme, ECMAScript, etc.),
which is nice.
Example:
--8<---cut here---start
