This ticket is really old, but the issue is still there. I'm closing this in
favor of https://github.com/rakudo/rakudo/issues/1234 (which is a new ticket
for the same issue but with a little bit more info).
On 2014-07-19 07:52:17, pesc...@gmail.com wrote:
> On Tue Oct 04 06:16:13 2011, coke wrote:
> > On Sat Jun 26 09:24:14 2010, moritz wrote:
> > > 18:21 <@moritz_> rakudo: say :foo<<string\ here>>.perl
> > > 18:21 <+p6eval> rakudo 142433: OUTPUT«"foo" => ("string\\",
> > > "here")␤»
> > > 18:21 <@moritz_> alpha: say :foo<<string\ here>>.perl
> > > 18:21 <+p6eval> alpha 30e0ed: OUTPUT«"foo" => "string here"␤»
> > > 18:21 <@moritz_> rakudobug!
> > >
> > > and even worse, silently swallows the backslash:
> > >
> > > 18:22 <@moritz_> rakudo: say «a\ b».perl
> > > 18:23 <+p6eval> rakudo 142433: OUTPUT«("a", "b")␤»
> >
> > Still failing the same way in rakudo 7408d6
>
> As of now, general backslash escapes seem to work inside << >>, e.g.
> \x, \o:
>
> 16:28 < psch> m: say <<\x61 \o142>> # this case works at least
> 16:28 <+camelia> rakudo-moar 866817: OUTPUT«a b␤»
>
> I suspect the original ticket is more about the interpretation of "\
> ". Niecza and Rakudo both currently assume that backslash-space means
> space:
>
> 16:32 <psch> p6: say "a\ b"
> 16:32 <camelia> rakudo-{parrot,jvm,moar} 866817, niecza v24-109-
> g48a8de3: OUTPUT«a b␤»
>
> I can see unspace inside qq Strings having at least one possible
> application, that of formatting a very long literal String in the
> source code, but I don't know if that's a useful enough feature to
> have, as "..." ~ \n "..." does it already.

Reply via email to