# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #130136] # in the subject line of all future correspondence about this issue. # <URL: https://rt.perl.org/Ticket/Display.html?id=130136 >
It seems like there is a lot of confusion going on with $nl vs $nl-in/$nl-out. This is especially a problem given that things do not complain if you pass a wrong named parameter to them (e.g. here nl is ignored: ｢open nl => “\r” …｣). There was an issue with our docs (see https://irclog.perlgeek.de/perl6/2016-11-19#i_13597877 ), which is now fixed. However, once I started grepping our docs to see if there are any other wrong mentions of $nl, I stumbled upon Proc. >From Proc source: ( https://github.com/rakudo/rakudo/blob/nom/src/core/Proc.pm ): submethod BUILD(…, Str:D :$nl = "\n", …) { … … … $!in = IO::Pipe.new(:proc(self), :path(''), :$chomp, nl-out => $nl); … … … $!out = IO::Pipe.new(:proc(self), :path(''), :$chomp, nl-in => $nl); … … … } So it seems like Proc can perfectly accept separate nl-in and nl-out, but for some reason it doesn't. My idea is that we should change it everywhere to nl-in/nl-out for consistency reasons. However, some sort backward compatibility thingy should be implemented so that we don't break existing code.
