unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jean Abou Samra <jean@abou-samra.fr>
To: Maxime Devos <maximedevos@telenet.be>,
	yarl baudig <yarl-baudig@mailoo.org>,
	guile-devel@gnu.org
Subject: Re: define-module, #:export and export
Date: Sat, 7 Jan 2023 17:24:00 +0100	[thread overview]
Message-ID: <805bb942-4e5d-e9ab-7f05-f9f4e665482a@abou-samra.fr> (raw)
In-Reply-To: <f9c593e3-a5f1-8345-3120-25d32b2ddc27@telenet.be>


[-- Attachment #1.1: Type: text/plain, Size: 673 bytes --]

Le 06/01/2023 à 14:55, Maxime Devos a écrit :
> Guile's implementation of macros is a little lax with typing,
> in the sense that objects like #false and #true (but not symbols, 
> because hygiene) can be returned too, but IIUC this is undocumented 
> and not standard Scheme (*).



Well, that is what I thought too, but after checking, I realize that it 
actually is standard. See

http://www.r6rs.org/final/html/r6rs-lib/r6rs-lib-Z-H-13.html

"""
More formally, a syntax object is:

- a pair of syntax objects,
-a vector of syntax objects,
- a nonpair, nonvector, nonsymbol value, or
- a wrapped syntax object.
"""

I learnt something today.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2023-01-07 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 15:11 define-module, #:export and export yarl baudig
2023-01-04 17:28 ` Maxime Devos
2023-01-05  2:07   ` Jean Abou Samra
2023-01-06 13:31     ` yarl baudig
2023-01-06 13:55       ` Maxime Devos
2023-01-07 16:24         ` Jean Abou Samra [this message]
2023-01-08  9:46           ` yarl baudig
2023-01-08 13:19             ` Jean Abou Samra
2023-01-08 15:18               ` yarl baudig
2023-01-08 15:23                 ` Jean Abou Samra
2023-01-13  7:58                   ` yarl baudig

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=805bb942-4e5d-e9ab-7f05-f9f4e665482a@abou-samra.fr \
    --to=jean@abou-samra.fr \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=yarl-baudig@mailoo.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).