On 24-02-2023 16:48, Ludovic Courtès wrote:
Maxime Devos skribis:
;; Before:
;; unknown file:#f:#f: syntax-stuff-twice: bad in subform
# of #
;; After:
;; [the same thing]
;;
;; Looks like another patch is needed ...
What backtrace are you trying to get?
Getting a backtrace showing
Maxime Devos skribis:
> ;; Before:
> ;; unknown file:#f:#f: syntax-stuff-twice: bad in subform
> # follow"> of # very hard to follow">
> ;; After:
> ;; [the same thing]
> ;;
> ;; Looks like another patch is needed ...
What backtrace are you trying to get?
Getting a backtrace showi
On 23-02-2023 12:38, Ludovic Courtès wrote:
Hi,
Maxime Devos skribis:
For complicated macros, especially macros that are used correctly but
have a bug in their implementation somewhere and use 'syntax-case'
or 'syntax-rules' multiple times, it can be very convenient to know
_which_ syntax-c
On 23-02-2023 12:38, Ludovic Courtès wrote:
Do you have a simple reproducer and a before/after comparison showing
what Guile prints?
(Please ignore my previous e-mail, the reproducer was incorrect. I'll
try making another one.)
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public ke
On 23-02-2023 12:38, Ludovic Courtès wrote:
Do you have a simple reproducer and a before/after comparison showing
what Guile prints?
Simpler reproducer:
(define-syntax syntax-stuff-twice
(lambda (s)
(define (f x)
(syntax-case x ()
(#:this #''this)
(#:that #''that)))
Hi,
Maxime Devos skribis:
> For complicated macros, especially macros that are used correctly but
> have a bug in their implementation somewhere and use 'syntax-case'
> or 'syntax-rules' multiple times, it can be very convenient to know
> _which_ syntax-case or syntax-rules raised the syntax-err