preliminary comments Peter McGoron (31 Aug 2026 13:12 UTC)
Re: preliminary comments Hernán Ibarra Mejia (01 Sep 2026 09:37 UTC)
Re: preliminary comments Peter McGoron (01 Sep 2026 11:10 UTC)
Re: preliminary comments Hernán Ibarra Mejia (02 Sep 2026 14:47 UTC)
Re: preliminary comments Peter McGoron (02 Sep 2026 15:18 UTC)
Re: preliminary comments Peter McGoron (01 Sep 2026 18:28 UTC)
Re: preliminary comments Hernán Ibarra Mejia (02 Sep 2026 15:14 UTC)
Re: preliminary comments Marc Nieper-Wißkirchen (03 Sep 2026 08:48 UTC)

Re: preliminary comments Hernán Ibarra Mejia 02 Sep 2026 14:47 UTC

On Tue Sep 1, 2026 at 2:06 PM EEST, Peter McGoron wrote:
> Auxiliary syntax is handled by the module system: for example, `(scheme
> base)` exports `=>`, `else`, and `...` as identifiers. This is because
> syntax-rules should match those identifiers hygienically (some macro
> expanders don't do this).

I think I am misunderstanding either you or the definition of "auxiliary
syntax". In the sample implementation [1], if I add `define/m` and `return/m` to
the export list I get an "unresolved identifier" error (I'm using CHICKEN 6
which is R7RS-small). I'd be grateful if you could check and clarify this for me
please.

Cheers,
Hernán

[1]: https://srfi.schemers.org/srfi-280/implementation.scm