New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bad .perl for paths with pipe characters #4877
Comments
From zefram@fysh.orgThe .perl method for IO::Path objects produces faulty output:
-zefram |
From @lizmat
$ 6 'say "/foo|\\bar".IO.perl.EVAL' Fixed with 8d50dabfa9a3b690b18a , test added with e41c6617855b61678544f9 , can be closed. Liz |
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgElizabeth Mattijsen via RT wrote:
Done the hard way. Because it lacks most of the refinements of The same method also has a similar escaping problem for $!CWD. Here the $.is-absolute -zefram |
From @lizmat
I see your point about escaping strings in a .perl. This has, however, much wider ramifications that will need to be checked. 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. The points about Liz |
From zefram@fysh.orgElizabeth Mattijsen via RT wrote:
I think you've misunderstood somewhere. The code that I proposed does For the main path attribute, calling .perl on the Str gets you one layer You got quoting right once already (Str.perl). Stop trying to do the -zefram |
From @lizmat
Indeed, it was a thinko, fixed in 12ba3410a13663b801c0
Don’t think so: if you interpolate a Str into a “”, then it calls the .Str method on it, *not* the .perl method. So the path part of the .perl is not .perlified just yet. Looking into that now. Liz |
From zefram@fysh.orgElizabeth Mattijsen via RT wrote:
I'm not sure where you think this is relevant. I was not expecting -zefram |
From @zoffixznetLooks like the mentioned have been fixed some time ago. Added another test for leading combiners for good measure, in Raku/roast@1ed18b4319 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126935 (status was 'resolved')
Searchable as RT126935$
The text was updated successfully, but these errors were encountered: