public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: Per Bothner <per@bothner.com>, kawa <kawa@sourceware.org>
Subject: Re: A bug in Kawa reader
Date: Fri, 03 Mar 2023 03:17:29 -0500	[thread overview]
Message-ID: <35395.1677831449@napur.eip10.org> (raw)
In-Reply-To: <CAMFYt2YpOX1n45fF_nX5ZqBin4Ny_92dN3feehFkmL+-QmBxkQ@mail.gmail.com>

On 2023-03-03T08:45:20+0100 (Friday), Panicz Maciej Godek via Kawa writes:
> czw., 2 mar 2023 o 23:30 Per Bothner <per@bothner.com> napisa=C5=82(a):
>
> >
> >
> > On 3/2/23 14:14, Panicz Maciej Godek via Kawa wrote:
> > > I've noticed that if there's an escaping slash at the end of a line
> > inside
> > > of a string, and the new line starts with white spaces, the white space=
> s
> > > will be chomped away from the resulting string
> >
> > That's an intended (and documented) feature.
> >
> >
> > https://www.gnu.org/software/kawa/String-literals.html#Simple-string-lite=
> rals
> >
> >
> You're right.
> I also checked it with the spec, and it doesn't determine this behavior.
>
> Kawa seems to behave like Gambit, Chicken and Chez in this regard,
> whereas Guile and Racket behave according to my expectation.
>
> Sorry for the noise.

I am not sure of the spec to which you refer but R7RS Section 6.7
includes, in the itemized list of escape sequences,

  \<intraline whitespace>*<line ending>
  <intraline whitespace>* : nothing

which is the behavior you observed in Kawa, etc.

I find it to be a useful feature for fitting long strings in nicely
indented code.

Regards,

-chaw

  reply	other threads:[~2023-03-03  8:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 22:14 Panicz Maciej Godek
2023-03-02 22:30 ` Per Bothner
2023-03-03  7:08   ` Damien Mattei
2023-03-03 17:05     ` Per Bothner
2023-09-18  5:09       ` Damien Mattei
2023-03-03  7:45   ` Panicz Maciej Godek
2023-03-03  8:17     ` Sudarshan S Chawathe [this message]
2023-03-03  8:29       ` Panicz Maciej Godek
2023-03-03 10:19     ` Lassi Kortela

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35395.1677831449@napur.eip10.org \
    --to=chaw@eip10.org \
    --cc=godek.maciek@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /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).