unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: No Itisnt <theseaisinhere@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: Custom printers for SRFI-9 records
Date: Wed, 26 May 2010 16:09:30 -0500	[thread overview]
Message-ID: <AANLkTilfCVtGl5arSJZQd7itU6nm7LKHdCMYv8rsF--5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikW--WRMvpnRIz3BxD1v06rAD1lUSQC7wpz6Kcz@mail.gmail.com>

Whoops ! Due to my misunderstanding of 'git push' I committed this to
master. I had already committed it to master locally so after I merge
it, I guess it pushed my master changes as well when I was trying to
push my lua branch.  Hopefully I didn't mess up anything else. I read
the docs now so it won't happen again.

On Tue, May 25, 2010 at 11:18 PM, No Itisnt <theseaisinhere@gmail.com> wrote:
> On Tue, May 25, 2010 at 3:56 PM, No Itisnt <theseaisinhere@gmail.com> wrote:
>> I agree. Here's a patch that adds (srfi srfi-9 gnu) with
>> set-record-printer! and adds a subsection to the SRFI-9 part of the
>> manual for it.
>> I can go ahead and commit it, if that's OK.
>>
>> On Tue, May 25, 2010 at 2:23 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> Hello!
>>>
>>> No Itisnt <theseaisinhere@gmail.com> writes:
>>>
>>>> One thing I'm missing, and maybe I just didn't see it, is a way to
>>>> define custom printers for SRFI-9 records.
>>>
>>> I agree that it’s generally useful, but I think SRFI modules should not
>>> diverge from the spec, or when they do, make it separate, as was done
>>> with (srfi srfi-4 gnu).
>>>
>>> What do you think?
>>>
>>> Thanks,
>>> Ludo’.
>>>
>>>
>>>
>>
>



  reply	other threads:[~2010-05-26 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  0:26 Custom printers for SRFI-9 records No Itisnt
2010-05-25 19:23 ` Ludovic Courtès
     [not found]   ` <AANLkTilzb959cEaRDcpFUntPK_r0q_9RsIE5pByG4QPm@mail.gmail.com>
2010-05-26  4:18     ` No Itisnt
2010-05-26 21:09       ` No Itisnt [this message]
2010-05-26 22:04         ` Ludovic Courtès
2010-05-26 22:42         ` Ludovic Courtès
2010-05-26 22:34       ` Ludovic Courtès
2010-05-27  2:41         ` No Itisnt
2010-05-27  8:20           ` Ludovic Courtès

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=AANLkTilfCVtGl5arSJZQd7itU6nm7LKHdCMYv8rsF--5@mail.gmail.com \
    --to=theseaisinhere@gmail.com \
    --cc=guile-devel@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).