From: Nala Ginrut <nalaginrut@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: global vars and #:declarative? (was [critical bug] The set! doesn't work in indirect reference)
Date: Thu, 19 Sep 2024 11:36:14 +0900 [thread overview]
Message-ID: <CAPjoZoee2TEHD6G7gP-7i67Rp34QJdt7Zv9MqKFbECqr6_wKMA@mail.gmail.com> (raw)
I realized the #:declarative? can only be applied in the downstream modules
of the module holding global vars.
So the #:declarative? will affect the whole module and I have to put it
everywhere that references the global vas.
Maybe it'd be better if there's finer granularity control for each, like
define-non-dclarative or else.
BTW. In my case, I want to implement the global var mutation. For such a
case, if users don't want to put #:declarative? to affect the whole
downstream modules, maybe the best way is to implement getter and setter
inside the global var module.
Comments are welcome.
Thanks!
Best regards.
next reply other threads:[~2024-09-19 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 2:36 Nala Ginrut [this message]
2024-09-19 6:56 ` global vars and #:declarative? (was [critical bug] The set! doesn't work in indirect reference) Dr. Arne Babenhauserheide
2024-09-19 12:30 ` Nala Ginrut
2024-09-19 15:33 ` Taylan Kammer
2024-09-20 4:40 ` Linus Björnstam
2024-09-22 2:34 ` Nala Ginrut
2024-09-22 18:57 ` Linus Björnstam
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=CAPjoZoee2TEHD6G7gP-7i67Rp34QJdt7Zv9MqKFbECqr6_wKMA@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.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).