unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Implement SRFI-105 curly infix expressions.
Date: Thu, 18 Oct 2012 17:09:44 -0400	[thread overview]
Message-ID: <87d30fpjvr.fsf@tines.lan> (raw)
In-Reply-To: <87txtrydg2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 18 Oct 2012 18:03:57 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>> My understanding was that the sweet-expressions folks already had
>>> something, no?
>>
>> The implementation they have (which they call a "demo") reimplements the
>> entire reader from scratch.  There are several problems with this, the
>> worst of which is that it strongly discourages anyone from using the
>> syntax in code that they'd like to deploy.  You can't simply publish a
>> module with '#!curly-infix' at the top and have people use it.  You have
>> to ask them to install the sweet-expressions implementation first, and
>> then ask them to somehow arrange for your code to be read using the
>> special reader.
>
> Would it help if it were distributed as part of Guile?  That’s something
> we could do when the implementation is considered reasonably stable.

That wouldn't work, because #!curly-infix (like any other reader
directive) can appear anywhere that comments are permitted, at any depth
within an s-expr, and must affect all tokens that follow until the end
of the file.

Even if we somehow figured out a way around that problem, the other
problem is that it would require us to maintain two almost identical
readers that implement all of the functionality our reader supports
(e.g. arrays, source properties, read-hash-extend, all of our other read
options, etc), and keep these two implementations in sync with each
other.

   Regards,
     Mark



      reply	other threads:[~2012-10-18 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14  9:18 [PATCH] Implement SRFI-105 curly infix expressions Mark H Weaver
2012-10-14 23:15 ` Mark H Weaver
2012-10-16 15:58 ` Ludovic Courtès
2012-10-16 20:38   ` Mark H Weaver
2012-10-18  7:16     ` nalaginrut
2012-10-18 16:03     ` Ludovic Courtès
2012-10-18 21:09       ` Mark H Weaver [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=87d30fpjvr.fsf@tines.lan \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).