From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SRFI-105 (curly-infix-expressions) marker #!srfi-105 ... could guile live with that?
Date: Wed, 05 Sep 2012 23:52:19 +0200 [thread overview]
Message-ID: <87pq60t9ws.fsf@gnu.org> (raw)
In-Reply-To: E1T95TV-0006ms-Pa@fenris.runbox.com
Hi David,
"David A. Wheeler" <dwheeler@dwheeler.com> skribis:
> Guile support for curly-infix-expressions is very important to me.
> Yet obviously guile has different semantics for #!, namely, #!...!#.
> Clearly #!srfi-105 could be handled by a special case, but could
> people live with that? I even have a notion for how "#!" could be
> implemented in a way that would consistently handle SRFI-22 (#!
> followed by space), guile's #!...!#, and things like #!fold-case, but
> I don't know if that would be ardently rejected or possibly accepted
> by guilers. The rationale (below) discusses this.
If that can be implemented without breaking backward compatibility, then
it’d be fine, I think.
Though I think out-of-band means should always work. For instance, when
compiling SRFI-105 code, one could write “guild compile --srfi-105
foo.sweet”, or
(compile #:from (lookup-language 'scheme-sweet-expressions) ...).
Thanks,
Ludo’.
prev parent reply other threads:[~2012-09-05 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 2:36 SRFI-105 (curly-infix-expressions) marker #!srfi-105 ... could guile live with that? David A. Wheeler
2012-09-05 7:09 ` svanleent
2012-09-05 12:12 ` David A. Wheeler
2012-09-07 7:18 ` Sjoerd van Leent Privé
2012-09-05 21: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=87pq60t9ws.fsf@gnu.org \
--to=ludo@gnu.org \
--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).