Re: A bug in Kawa reader

[Panicz Maciej Godek <godek.maciek@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

pt., 3 mar 2023 o 09:17 Sudarshan S Chawathe <chaw@eip10.org> napisał(a):

> 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 checked with R5RS, which said (in section 6.3.5):

"Scheme does not specify the effect of a backslash within a string that is
not followed by a doublequote or backslash."


> I find it to be a useful feature for fitting long strings in nicely
> indented code.
>
> I've found it quite surprising, to be honest.