From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Block comments and `read-hash-extend'
Date: Mon, 05 Sep 2005 02:02:00 +0300 [thread overview]
Message-ID: <871x4477yv.fsf@zagadka.de> (raw)
In-Reply-To: <87k6kumykq.fsf@laas.fr> (Ludovic Courtès's message of "Thu, 16 Jun 2005 11:37:57 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Comments?
Your patch has the problem that it breaks things like
(+ 2 2 #! 2 !#)
We can still support the #! read-hash extension, of course, which I
think is a good idea.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-09-04 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 9:37 Block comments and `read-hash-extend' Ludovic Courtès
2005-06-17 0:13 ` Kevin Ryde
2005-06-17 7:31 ` Ludovic Courtès
2005-06-17 22:40 ` Rob Browning
2005-09-04 22:59 ` Marius Vollmer
2005-09-04 23:57 ` Rob Browning
2005-07-04 22:26 ` Neil Jerram
2005-08-19 8:11 ` Ludovic Courtès
2005-09-04 23:02 ` Marius Vollmer [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=871x4477yv.fsf@zagadka.de \
--to=mvo@zagadka.de \
--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).