[perl #126935] [BUG] bad .perl for paths with pipe characters

2017-04-30 Thread Zoffix Znet via RT
Looks like the mentioned have been fixed some time ago. Added another test for leading combiners for good measure, in https://github.com/perl6/roast/commit/1ed18b4319

[perl #126935] [BUG] bad .perl for paths with pipe characters

2017-04-30 Thread Zoffix Znet via RT
Looks like the mentioned have been fixed some time ago. Added another test for leading combiners for good measure, in https://github.com/perl6/roast/commit/1ed18b4319

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Zefram
Elizabeth Mattijsen via RT wrote: >Don't think so: if you interpolate a Str into a "", then it calls the >.Str method on it, *not* the .perl method. I'm not sure where you think this is relevant. I was not expecting implicit .perl calls from any interpolation. The code that I proposed interpolat

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Elizabeth Mattijsen
> On 17 Dec 2015, at 17:31, Zefram wrote: > > Elizabeth Mattijsen via RT wrote: >> In any case, Str.perl cannot be used, because it puts double quotes >> around it. Which would be a set of double quotes too many. > > I think you've misunderstood somewhere. The code that I proposed does > not h

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Zefram
Elizabeth Mattijsen via RT wrote: >In any case, Str.perl cannot be used, because it puts double quotes >around it. Which would be a set of double quotes too many. I think you've misunderstood somewhere. The code that I proposed does not have a multiple-quotation bug, but what you've committed *d

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Elizabeth Mattijsen
> On 17 Dec 2015, at 16:16, Zefram wrote: > > Elizabeth Mattijsen via RT wrote: >> Fixed with 8d50dabfa9a3b690b18a > > Done the hard way. Because it lacks most of the refinements of > Str.perl, it looks like it might still have bugs that Str.perl avoids. > For example, leading combining charact

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Zefram
Elizabeth Mattijsen via RT wrote: >Fixed with 8d50dabfa9a3b690b18a Done the hard way. Because it lacks most of the refinements of Str.perl, it looks like it might still have bugs that Str.perl avoids. For example, leading combining characters will become part of the grapheme of the opening delimi

Re: [perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-17 Thread Elizabeth Mattijsen
> On 16 Dec 2015, at 12:31, Zefram (via RT) > wrote: > > # New Ticket Created by Zefram > # Please include the string: [perl #126935] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=126935 > > > > The .perl method for IO

[perl #126935] [BUG] bad .perl for paths with pipe characters

2015-12-16 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #126935] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126935 > The .perl method for IO::Path objects produces faulty output: > "/foo|bar".IO.perl q|/foo|bar|