From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Print backtraces for syntax errors too.
Date: Fri, 24 Feb 2023 16:48:24 +0100 [thread overview]
Message-ID: <871qmf2hfb.fsf@gnu.org> (raw)
In-Reply-To: 1616ff0f-691a-7bcd-f1af-abff0e6a8753@telenet.be
Maxime Devos <maximedevos@telenet.be> skribis:
> ;; Before:
> ;; unknown file:#f:#f: syntax-stuff-twice: bad in subform
> #<syntax:reproducer.scm:15:27 "imagine this syntax is very hard to
> follow"> of #<syntax:reproducer.scm:15:27 "imagine this syntax is
> very hard to follow">
> ;; After:
> ;; [the same thing]
> ;;
> ;; Looks like another patch is needed ...
What backtrace are you trying to get?
Getting a backtrace showing which macros are being expanded (similar to
what GCC does) would be great, but it’s much more work; changing this
one line in libguile won’t achieve that.
Ludo’.
next prev parent reply other threads:[~2023-02-24 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:59 [PATCH] Print backtraces for syntax errors too Maxime Devos
2023-02-23 11:38 ` Ludovic Courtès
2023-02-23 19:04 ` Maxime Devos
2023-02-23 19:10 ` Maxime Devos
2023-02-23 19:27 ` Maxime Devos
2023-02-24 15:48 ` Ludovic Courtès [this message]
2023-02-24 23:38 ` Maxime Devos
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qmf2hfb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).