I have done some research on this issue. The "correct" behavior seems
to be to match what Windows would do in cmd.exe. That would provide
the users with the least surprise.
Michael Kaplan's guidance[1] on file names seems to also describe how
Windows handles names of environment variables:
> For
I have observed this before (including with the 2017.01 release), but
most recently today after building from a fresh pull.
$ perl6 -v
This is Rakudo version 2017.02-140-gdd1dab2 built on MoarVM version
2017.02-20-g773711e
implementing Perl 6.c.
$ nqp -v
This is nqp version 2017.02-39-g2780ed7 bu
For reference, note
https://rt.perl.org/Public/Bug/Display.html?id=126881 and
https://www.nu42.com/2015/12/perl6-newline-translation-broken.html
I thought this was behind us.
-- Sinan
On Wed, Feb 15, 2017 at 3:40 PM, Zoffix Znet via RT
wrote:
> Looks like several other tests in S17-procasync/basic.t would be failing as
> well if it weren't for the explicit kludges[^1][^2] added to replace "\r\n"
> to "\n".
*Sigh* ... I was in a hurry, so I did not look.
This is disappointin
I am not sure what the right strategy is ... Perl 5 seems to work
mainly because they use the ANSI interfaces to get environment
variables ... which means you can't get the value of $ENV{iş}.
I opened this issue because I am going to think about it and thought
there should be something to referenc
https://github.com/MoarVM/MoarVM/pull/528/files?diff=split
was merged so this ticket can be closed. Thank you.
-- Sinan
I think my pull request has reached the point where it should work on
others' machines, too ;-)
Please try it out:
https://github.com/MoarVM/MoarVM/pull/528/files?diff=split
See also https://github.com/MoarVM/MoarVM/issues/527
@Parrot Raiser, please see
https://github.com/perl6/nqp/issues/346#issuecomment-278090170
https://github.com/perl6/nqp/issues/346#issuecomment-278102220
https://github.com/perl6/nqp/issues/346#issuecomment-278104580
-- Sinan
I created this report by mistake when I was hastily trying to follow-up on
https://rt.perl.org/Public/Bug/Display.html?id=127925
The reply belongs there. I would appreciate it if you could merge this
ticket with the correct one.
Apologies and thank you.
I will test again as soon as I can. Thank you.
On Fri, Jul 29, 2016 at 4:30 PM, Stefan Seifert via RT
wrote:
> Can you please re-test? Similar failures were reportedly fixed by commit
> 43debec892f0bdaf0c474d09c5805d1015fcae6d but I have no Windows system to test
> on.
> I am afraid I do not know where to go from here, but FYI.
Pull request submitted. I hope this is the right place to do that:
https://github.com/perl6/roast/pull/87
The fix I propose is to invoke methods on $*SPEC rather than IO::Spec.
HTH,
-- Sinan
> I am afraid I do not know where to go from here, but FYI.
Pull request submitted. I hope this is the right place to do that:
https://github.com/perl6/roast/pull/87
The fix I propose is to invoke methods on $*SPEC rather than IO::Spec.
HTH,
-- Sinan
13 matches
Mail list logo
