I will check it.
]]>BEGIN {
die "Error";
}
die "OS unsupported" unless $^O eq 'darwin';
]]>Currently, I do like this. CPAN testers report is UNKNOWN.
I want NA.
# SPVM only support 64bit integer Perl
my $ivsize = $Config{ivsize};
if ($ivsize
die "SPVM don't support the Perl which \"ivsize\" is lower than 8";
}
# SPVM only support NetBSD 7+
if ($Config{osname} eq 'netbsd' && $Config{osvers}
die "SPVM don't support NetBSD 6, 5, 4, 3, 2, 1";
}
In this case, I get NA
I think this would send several messages to the outside world:
Thoughts ?
]]>As for the new name I don't particularly like Raku. For a Brazilian Portuguese speaker it sounds harsh. But I think it's mostly about having time to get used to it.
Some time ago I thought that "Gerl" would be a nice name for Perl 6:
On the other hand, the new name should probably be very different from Perl in order to avoid perpetuating the confusion. Raku fits this bill very well.
So be it.
]]>I mean, the big user-visible improvement in Perl 5.30 was "The upper limit 'n' specifiable in a regular expression quantifier of the form '{m,n}' has been doubled to 65534", which was pretty underwhelming. And so far, the most notable change in the dev releases is that "vec" is not allowed on code points above 0xFF. I'm sure these are good and valuable changes, and yet at the same time, it's not exactly what I'd want to see in a "What's new in Perl 7" document.
]]>file://foo/bar
". Even though I know it's trusted I still get:
Warning: checksum file '/mnt/CPAN/authors/id/G/GB/GBARR/CHECKSUMS' not conforming.
The cksum does not contain the key 'cpan_path' for 'CPAN-DistnameInfo-0.12.tar.gz'.
Proceed nonetheless? [no]
How can I handle this scenario?
]]>Also, the sponsors page at http://iheart.cpantesters.org/ is showing an error and has been for many months, likely because it too depends on the now-gone EPO site. I've raised this problem elsewhere previously but perhaps you could also have a word?
]]>