From: jbranso@dismail.de
To: "jgart" <jgart@dismail.de>
Cc: "Guix Help" <help-guix@gnu.org>
Subject: Re: How can I step through this code?
Date: Sun, 09 Oct 2022 00:14:23 +0000 [thread overview]
Message-ID: <d61b9e0b11d2e2892c41bd1d6cd3b6a7@dismail.de> (raw)
In-Reply-To: <20221008122346.GB17635@dismail.de>
October 8, 2022 1:23 PM, "jgart" <jgart@dismail.de> wrote:
> On Sat, 08 Oct 2022 15:03:54 +0000 jbranso@dismail.de wrote:
>
>> That's smart!
>
> Did you try it? I've been trying to understand how some Guile code works
> by just throwing it in the Racket debugger. It doesn't always work but
> when it does it's like driving a fancy cadillac through the stack.
hahaha! I have not tried it. I definitely should.
I ran into this common problem yesterday. I am of course simplifying:
(string-append "hello"
(if some-var
" world\n"))
error: expecting type string
(string-append "hello" #unspecified)
It took me an embarrassing amount of time to track down where the
#unspecified was coming from.
I feel like the error message was a little bit cryptic. It said that
one particular function cause the error...It just took me a while to track
it down. A debugger stepping through the code would have been awesome!
> It's too bad that Guile's debugger sucks compared to Racket's debugger. Maybe
> someday someone will implement something amazing for that.
>
> RE The Common Lisp debugger: It's really great but it might be a rabbit hole.
>
> I recommend using sly or slime with sbcl if you want to go down that.
Right now I am super in love with Guix. My main squeeze is working
on our existing opensmtpd-service and letting users configure it with
proper scheme records. I don't know if I want to play with common lisp.
Thanks,
Joshua
next prev parent reply other threads:[~2022-10-09 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 3:05 How can I step through this code? jgart
2022-10-07 18:45 ` jbranso
2022-10-07 19:22 ` jgart
2022-10-07 21:52 ` jbranso
2022-10-08 1:25 ` jgart
2022-10-08 15:03 ` jbranso
2022-10-08 17:23 ` jgart
2022-10-09 0:14 ` jbranso [this message]
2022-10-09 16:30 ` jgart
2022-10-10 19:49 ` jbranso
2022-10-10 22:40 ` jgart
2022-10-10 16:04 ` Ludovic Courtès
2022-10-10 17:00 ` jgart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d61b9e0b11d2e2892c41bd1d6cd3b6a7@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.