Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 11:46 UTC)
Re: Edge case in SRFI-139 Marc Nieper-Wißkirchen (28 Jan 2024 12:31 UTC)
Re: Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 14:09 UTC)
Re: Edge case in SRFI-139 Marc Nieper-Wißkirchen (28 Jan 2024 14:43 UTC)
Re: Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 16:12 UTC)
Re: Edge case in SRFI-139 Marc Nieper-Wißkirchen (28 Jan 2024 16:20 UTC)
Re: Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 16:22 UTC)
Re: Edge case in SRFI-139 Marc Nieper-Wißkirchen (28 Jan 2024 16:28 UTC)
Re: Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 17:56 UTC)
Re: Edge case in SRFI-139 Jakub T. Jankiewicz (28 Jan 2024 16:39 UTC)
Re: Edge case in SRFI-139 Shawn Wagner (28 Jan 2024 16:57 UTC)

Re: Edge case in SRFI-139 Jakub T. Jankiewicz 28 Jan 2024 17:56 UTC

On Sun, 28 Jan 2024 17:27:58 +0100
Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:

> What do you mean by #<syntax-rules> object? You cannot access the
> transformer associated with a keyword through standard means.

This is limitation of my implementation, I didn't know any better so in my
implementation Macros are runtime, they work like function calls but return
code that can be evaluated. I plan to change it in the future and write
proper expander. So right now you can print the macro and get #<syntax>
object.

That's why in my implementation you can use define to create an alias for the
macro:

(define define-syntax-parameter define-syntax)

Sometimes it's helpful but it give problems with hygienic macros.

--
Jakub T. Jankiewicz, Senior Front-End Developer
https://jcubic.pl/me
https://lips.js.org
https://koduj.org