unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	Guile User <guile-user@gnu.org>
Subject: Re: Weird cache issue
Date: Tue, 15 Mar 2022 20:10:53 +0100	[thread overview]
Message-ID: <0388e2345cc16f976bb2e3f9c54bf97cc8455a52.camel@telenet.be> (raw)
In-Reply-To: <857fc700-4ac5-fa7b-1306-cccda26f0d58@posteo.de>

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

Zelphir Kaltstahl schreef op di 15-03-2022 om 17:54 [+0000]:
> ~~~~013.scm~~~~
> (library (fileio)
>    (export )
>    (import
>     (except (rnrs base) let-values)
>     (only (guile)
>           lambda* λ
>           ;; printing
>           display
>           simple-format)
>     (fileio)))

Shouldn't the code below be put inside the library form?
While these imports might be available below as well due to
how 'library' is 'define-module' followed by some extra code
(see ice-9/r6rs-libraries.scm), it is not something you can
rely upon:

             ;; It would be nice to push the module that was current before the
             ;; definition, and pop it after the library definition, but I
             ;; actually can't see a way to do that. Helper procedures perhaps,
             ;; around a fluid that is rebound in save-module-excursion? Patches
             ;; welcome!

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-03-15 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 17:54 Weird cache issue Zelphir Kaltstahl
2022-03-15 19:04 ` Maxime Devos
2022-03-15 22:45   ` Zelphir Kaltstahl
2022-03-15 19:06 ` Maxime Devos
2022-03-15 19:10 ` Maxime Devos [this message]
2022-03-15 22:44   ` Zelphir Kaltstahl

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=0388e2345cc16f976bb2e3f9c54bf97cc8455a52.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-user@gnu.org \
    --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).