From: Stephen Compall <s11@member.fsf.org>
Cc: Paul Jarc <prj@po.cwru.edu>, guile-devel@gnu.org
Subject: Re: Unrecognized \ sequences and Elisp
Date: 27 Jan 2004 11:43:49 -0600 [thread overview]
Message-ID: <xfyhdyh8ey2.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <1075207814.23541.1113.camel@localhost>
Roland Orre <orre@nada.kth.se> (not really) writes:
> > Well, if we see the two characters \( in the middle of a string, then
> > the program is not portable, and we have to decide on our own what to
> > do about it. Treating it like plain ( eliminates the possibility of
> > future extensions, so now Guile has been changed to throw an error -
> > i.e., it refuses to interpret this escape sequence at all. Isn't that
> > what you want?
Speaking of future extensions, why not just make this extensible,
then, and use the needed extensions when reading elisp?
--
Stephen Compall or s11 or sirian
If it were thought that anything I wrote was influenced by Robert Frost,
I would take that particular work of mine, shred it, and flush it down
the toilet, hoping not to clog the pipes. A more sententious, holding-
forth old bore who expected every hero-worshiping adenoidal little twerp
of a student-poet to hang on to his every word I never saw.
-- James Dickey
UFO STARLAN Glock Leitrim military event security Audiotel Marxist
genetic defense information warfare MDA Panama BROMURE MD5 Firefly
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-27 17:43 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 [this message]
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
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=xfyhdyh8ey2.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
--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).