From: Marius Vollmer <mvo@zagadka.de>
Cc: Paul Jarc <prj@po.cwru.edu>, guile-devel@gnu.org
Subject: Re: Unrecognized \ sequences and Elisp
Date: Sun, 08 Feb 2004 23:06:07 +0100 [thread overview]
Message-ID: <87ptcpns4w.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m31xp5idph.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "08 Feb 2004 19:16:42 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> In the absence of any responses, I've committed this change:
>
> * read.c (scm_read_opts): New opts `elisp-vectors' and
> `escaped-parens'.
What about having 'elisp-strings' instead escaped-parens?
Escaped-parens seems very, very specific to me but still its only use
is to allow the reading of elisp strings.
In the long run, I think we should have a configurable reader, much
like Common Lisp specifies it.
> Because it is declared with SCM_API, I've taken care, and introduced a
> slight extra complexity, to preserve the interface of scm_lreadparen.
> Is this really necessary?
It is a good thing to do, but i this case, not strictly necessary, I'd
say. You could also have renamed scm_lreadparen to scm_i_lreadparen
(or made it static, maybe) and thus removed it from the public
interface of libguile.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-08 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 3:37 Fwd: Re: Unrecognized \ sequences and Elisp Roland Orre
2004-01-27 9:04 ` Paul Jarc
2004-01-27 12:50 ` Roland Orre
2004-01-27 16:26 ` tomas
2004-01-27 17:43 ` Stephen Compall
2004-01-28 17:03 ` Neil Jerram
2004-02-08 19:16 ` Neil Jerram
2004-02-08 22:06 ` Marius Vollmer [this message]
2004-02-10 19:27 ` Neil Jerram
2004-02-18 21:10 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2004-01-26 23:26 Neil Jerram
2004-01-27 2:45 ` Paul Jarc
2004-01-27 6:44 ` Stephen Compall
2004-01-27 8:55 ` Paul Jarc
2004-01-28 16:32 ` Neil Jerram
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=87ptcpns4w.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
--cc=prj@po.cwru.edu \
/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).