unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Keith Wright <kwright@keithdiane.us>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-user@gnu.org
Subject: Re: Ideas for making Guile easier to approach
Date: Wed, 09 Feb 2022 18:06:44 -0500	[thread overview]
Message-ID: <87tud7skqj.fsf@fcs22.keithdiane.us> (raw)
In-Reply-To: <0e1b4d4f7b0e097870326da44d4f51be3b6a1b98.camel@telenet.be> (message from Maxime Devos on Wed, 09 Feb 2022 22:05:05 +0100)

Maxime Devos <maximedevos@telenet.be> writes:

> Christine Lemmer-Webber schreef op wo 09-02-2022 om 10:18 [-0500]:
>> We had:
>> 
>>     #:use-module (srfi args-fold)
>>     #:use-module (srfi streams)
>>     #:use-module (srfi tests))
>
> The RnRS reserved the (srfi ...) namespace for the SRFI process,

I don't know off-hand if that's true, but it's a good idea...

> possibly adding our own names here would be against the standard.

...and not a problem.   Pick a new name for your new thing.

>>     #:use-module (guile-srfi args-fold)
>>     #:use-module (guile-srfi streams)
>>     #:use-module (guile-srfi tests))

That's just as easy to follo9w, and you know what this meains:

>>     #:use-module (chicken-srfi lazy-streams)
>>     #:use-module (s48-srfi tests))

and you know where to put any little thing needed to
translate s48 tests to guile tests if inconsistencies are found.

   -- Keith
 



  reply	other threads:[~2022-02-09 23:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 12:19 Newbie thoughts on Guile Hall + Guix Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09 15:18   ` Ideas for making Guile easier to approach Christine Lemmer-Webber
2022-02-09 20:33     ` Daniel Tornabene
2022-02-09 21:05     ` Maxime Devos
2022-02-09 23:06       ` Keith Wright [this message]
2022-02-09 21:05     ` Olivier Dion via General Guile related discussions
2022-02-09 21:07     ` Maxime Devos
2023-10-05 14:15       ` Dr. Arne Babenhauserheide
2022-02-09 23:01     ` Chris Vine
2022-02-10  0:56     ` Timothy Sample
2022-02-10 10:01       ` Ricardo Wurmus
2022-02-10  1:32     ` Blake Shaw
2022-02-10  2:02     ` paul
2022-02-10 11:27     ` Mikael Djurfeldt
2022-02-10 14:34       ` Leo Butler
2022-02-10 15:58         ` Mikael Djurfeldt
2022-02-10 18:25         ` Olivier Dion via General Guile related discussions
2023-09-27 19:29     ` Christine Lemmer-Webber
2023-09-28 12:30       ` Maxime Devos
2022-02-09  6:28 ` Newbie thoughts on Guile Hall + Guix Catonano

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=87tud7skqj.fsf@fcs22.keithdiane.us \
    --to=kwright@keithdiane.us \
    --cc=guile-user@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).