From: Jean Abou Samra <jean@abou-samra.fr>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
Guile User <guile-user@gnu.org>
Subject: Re: Understanding `symbol??` macro from okmij.org
Date: Thu, 14 Mar 2024 16:57:08 +0100 [thread overview]
Message-ID: <52B19FA3-244D-4734-80C7-E074F091DC4D@abou-samra.fr> (raw)
In-Reply-To: <87sf0sx3up.fsf@laura>
> Excuse my ignorance, by why is symbol?? not written using syntax-cases
> and the `indentifier?' guard?
a) Because it's intellectually interesting to see what the power of syntax-rules is :)
b) Not all Scheme standards and implementations contain syntax-case.
next prev parent reply other threads:[~2024-03-14 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 0:18 Understanding `symbol??` macro from okmij.org Zelphir Kaltstahl
2024-03-14 1:01 ` Jean Abou Samra
2024-03-14 1:03 ` Maxime Devos
2024-03-14 13:46 ` Zelphir Kaltstahl
2024-03-14 14:52 ` Olivier Dion
2024-03-14 15:57 ` Jean Abou Samra [this message]
2024-03-14 16:39 ` Olivier Dion
2024-03-14 18:01 ` Jean Abou Samra
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=52B19FA3-244D-4734-80C7-E074F091DC4D@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=zelphirkaltstahl@posteo.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.
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).