From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Paul Jarc <prj@po.cwru.edu>, guile-devel@gnu.org
Subject: Re: Unrecognized \ sequences and Elisp
Date: 10 Feb 2004 19:27:11 +0000 [thread overview]
Message-ID: <m37jyuhh0w.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <87ptcpns4w.fsf@zagadka.ping.de>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.de> writes:
Marius> What about having 'elisp-strings' instead escaped-parens?
Marius> Escaped-parens seems very, very specific to me but still its only use
Marius> is to allow the reading of elisp strings.
OK, I'll make this change.
Marius> In the long run, I think we should have a configurable reader, much
Marius> like Common Lisp specifies it.
Can you give a reference?
>> 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?
Marius> It is a good thing to do, but i this case, not strictly necessary, I'd
Marius> say. You could also have renamed scm_lreadparen to scm_i_lreadparen
Marius> (or made it static, maybe) and thus removed it from the public
Marius> interface of libguile.
So ...
(1) In this case, should I simplify my change by:
- eliminating scm_lreadparen (as it is now)
- renaming scm_lreadparen1 to scm_lreadparen
- making scm_lreadparen static?
(2) In general, how do users know what in the C API we are trying to
preserve? (I think the answer should be "whatever is documented
in the manual", but currently that probably doesn't cover enough.)
Thanks,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-10 19:27 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
2004-02-10 19:27 ` Neil Jerram [this message]
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=m37jyuhh0w.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).