unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: What does #-3# mean?
Date: Wed, 25 Aug 2010 11:52:05 +0200	[thread overview]
Message-ID: <87occrm33u.fsf@gnu.org> (raw)
In-Reply-To: <87occr1vek.fsf@delenn.lan> (Andreas Rottmann's message of "Wed,  25 Aug 2010 00:46:27 +0200")

Hello,

Andreas Rottmann <a.rottmann@gmx.at> writes:

> "dskr@mac.com" <dskr@mac.com> writes:
>
>> I recall that the reader can be hash-extended to read these forms in a
>> hacky way. Extend on '-'. I don't recall exactly anymore. I long ago
>> patched the reader to read these natively. Perhaps there is some
>> enthusiasm for making these readable in the main line?
>>
> I'd like to implement SRFI-38, and perhaps the best way would be to
> modify the core reader/writer, instead of adding something like the
> reference implementation? Would this require a new reader option, or
> should it be always enabled?

I’d do it using either ‘read-hash-extend’, which should make it possible
to implement ‘read-with-shared-structure’ without touching ‘read’ (or
I’d take this opportunity to write a new ‘read’ in Scheme using SILex.
:-))

Thanks,
Ludo’.



      reply	other threads:[~2010-08-25  9:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 16:03 What does #-3# mean? Richard Shann
2010-08-24 16:38 ` Ludovic Courtès
2010-08-24 20:46   ` dskr
2010-08-24 22:46     ` Andreas Rottmann
2010-08-25  9:52       ` Ludovic Courtès [this message]

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=87occrm33u.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=a.rottmann@gmx.at \
    --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).