From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-devel@gnu.org
Subject: Re: Fwd: Re: Unrecognized \ sequences and Elisp
Date: Tue, 27 Jan 2004 04:04:23 -0500 [thread overview]
Message-ID: <m3d695ep8y.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <1075174623.23547.960.camel@localhost>
Roland Orre <orre@nada.kth.se> wrote:
> R5RS defines only \\ and \"; ``Scheme does not specify the effect
> of a backslash within a string that is not followed by a
> doublequote or backslash.
Then portable programs cannot use other escape sequences, which means
that implementations can invent meanings for other escape sequences
without breaking portable programs.
> I consider the reason for escape sequences in strings is to be able
> to express a " within a string, i.e. to be able to express a
> character that we would otherwise not be able to put in the string.
They're also useful for representing characters that would be
difficult to work with literally - control characters, etc.
> I consider that it is better to have routines like read-ansi-string
> and write-ansi-string, which was previously suggested,
Do you have a reference? I don't know what those are intended to do,
but it doesn't sound like the same job that escape sequences do.
> general interpretation of escape sequences within strings will
> affect the general handling of strings in different applications.
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?
paul
_______________________________________________
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 9:04 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2004-02-18 21:10 ` Marius Vollmer
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=m3d695ep8y.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--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).