unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "Taylan Kammer" <taylan.kammer@gmail.com>,
	"Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>,
	"guile-devel@gnu.org" <guile-devel@gnu.org>,
	"Lassi Kortela" <lassi@lassi.io>
Subject: Re: Are library names data or syntax?
Date: Mon, 22 Jul 2024 23:05:30 +0200	[thread overview]
Message-ID: <875xsxi1d1.fsf@web.de> (raw)
In-Reply-To: <20240722204721.qinL2C00T2kuPDg01inMky@xavier.telenet-ops.be> (Maxime Devos's message of "Mon, 22 Jul 2024 20:47:25 +0200")

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Maxime Devos <maximedevos@telenet.be> writes:
> * hence, you can define a module from within another module (might be
> situationally useful, but comes with new difficulties for module
> lookup)

I actually tried something in that direction in enter three witches —
and failed.

I wanted to add a macro that maps

SCENE I

to defining a module that cleanly separates different parts of a story.

But I didn’t get that to work well (because it would have had to add
automatic exports and canonical imports and all together caused more
problems than it solved.

Or maybe I didn’t understand well enough what I was doing. Generating
code that generates modules isn’t a good idea if there’s a similar
option that uses standard mechanisms.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2024-07-22 21:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1941.1721507730.3505.guile-devel@gnu.org>
2024-07-21  9:54 ` guile-devel Digest, Vol 260, Issue 25 Marc Nieper-Wißkirchen
2024-07-22  8:12   ` Are library names data or syntax? Taylan Kammer
2024-07-22  9:14     ` Marc Nieper-Wißkirchen
2024-07-22 17:43       ` Numbers in library names Lassi Kortela
2024-07-22 17:56         ` Marc Nieper-Wißkirchen
2024-07-22 18:12           ` Lassi Kortela
2024-07-22 18:47             ` Maxime Devos
2024-07-22 20:52               ` Artyom Bologov
2024-07-22 21:01                 ` Marc Nieper-Wißkirchen
2024-07-22 21:05                   ` Artyom Bologov
2024-07-22 21:09             ` Marc Nieper-Wißkirchen
2024-07-23 15:05               ` Lassi Kortela
2024-07-23 15:16                 ` Marc Nieper-Wißkirchen
2024-07-23 15:36                   ` Lassi Kortela
2024-07-23 16:01                     ` Maxime Devos
2024-07-23 16:12                       ` Lassi Kortela
2024-07-23 16:20                         ` Maxime Devos
2024-07-22 18:47     ` Are library names data or syntax? Maxime Devos
2024-07-22 21:05       ` Dr. Arne Babenhauserheide [this message]
2024-07-22 21:14         ` Marc Nieper-Wißkirchen
2024-07-23 14:42       ` Marc Nieper-Wißkirchen

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=875xsxi1d1.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-devel@gnu.org \
    --cc=lassi@lassi.io \
    --cc=marc@nieper-wisskirchen.de \
    --cc=maximedevos@telenet.be \
    --cc=taylan.kammer@gmail.com \
    /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).