Re: How do people debug their guile code?

[Fredrik Salomonsson <plattfot@posteo.net>]

Hi Zelphir,

Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:

> I've not used guile-hall yet, nor tested with it.

It has some rough edges but keeps my focus away from hacking on build
system files (which I tend to do far too much). So I'm digging it.

> However, what I do to reproduce the same environment as I have in
> srfi-64 unit test, but inside the REPL is the following:
>
> 1. start the Guile REPL with `guile -L <dir where my module is>`
> 2. run `(use-modules (<my module name>))`
> 3. use procedures defined inside the module
> 4. copy and paste changed or new definitions from the code
> 5. try out the definitions and if something goes wrong fix it and go
> back to step 4 again
>
> If running M-x run-guile or M-x run-geiser from Emacs, one might need to
> change the %load-path of Guile. This can be done with `(add-to-load-path
> <string path to dir containing my module>)` for example. Then one can
> proceed as described above again.
>
> Not sure if any of this is new to you, but I guessed it would be good to
> put it out there.

Thanks for the write up. I know most of the pieces, from reading the
manual. But I'm still trying to piece them together so this is very
helpful for me. Especially the "add-to-load-path" for geiser, as that is
what I was missing.

-- 
s/Fred[re]+i[ck]+/Fredrik/g