unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Taylan Kammer" <taylan.kammer@gmail.com>, lloda <lloda@sarc.name>
Cc: 39601@debbugs.gnu.org, pclouds@gmail.com
Subject: bug#39601: srfi library naming in r7rs
Date: Wed, 03 Nov 2021 08:37:30 +0100	[thread overview]
Message-ID: <5632b6dc-6b83-44ed-b6f6-23eca0239a26@www.fastmail.com> (raw)
In-Reply-To: <e826c6a9-ee7a-b9c2-c46f-a799b864bc03@gmail.com>

Well, as someone who has written a lot of macros https://srfi.schemers.org/srfi-206/ is a fantastic utility SRFI. It allows several libraries to define the same aux syntax (say like srfi-26's <>) without having collisions.

That is not strictly what you were looking for if I understand the patch correctly, though.

-- 
  Linus Björnstam

On Mon, 1 Nov 2021, at 19:42, Taylan Kammer wrote:
> On 01.11.2021 18:52, lloda wrote:
>> 
>> Hi Taylan,
>> 
>> Your patch leaks a bunch of identifiers, could you fix that?
>> 
>> thanks
>> 
>> 	Daniel
>> 
>
> Apparently anything defined in boot-9 is implicitly made public in
> the (guile) module, I wasn't aware of that.
>
> Is there a work-around that allows one to define helpers that can
> be used by multiple definitions?
>
> Attached is a naive fix that duplicates a bunch of helpers which is
> not very nice.
>
> -- 
> Taylan
> Attachments:
> * 0001-Improve-support-for-R6-R7-SRFI-module-name-formats.patch





  parent reply	other threads:[~2021-11-03  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 12:54 bug#51264: Calling ‘texi-fragment->stexi’ in parallel leads to crashes Ludovic Courtès
2021-10-22 11:56 ` Ludovic Courtès
2021-11-01 17:52 ` bug#39601: srfi library naming in r7rs lloda
2021-11-01 18:42   ` Taylan Kammer
2021-11-02 17:53     ` lloda
2021-11-03  7:37     ` Linus Björnstam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-14 14:48 Duy Nguyen
2021-05-15 17:44 ` Taylan Kammer

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=5632b6dc-6b83-44ed-b6f6-23eca0239a26@www.fastmail.com \
    --to=linus.bjornstam@veryfast.biz \
    --cc=39601@debbugs.gnu.org \
    --cc=lloda@sarc.name \
    --cc=pclouds@gmail.com \
    --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).