Leon Timmermans
Leon Timmermans
> The error in the ls command prevents Perl from passing the integrity check I'm not sure where that conclusion comes from? That error is strongly suggesting it comes from...
@Tux you have any ideas?
Essentially this is because our install system doesn't have a concept of a section 7, only sections 1 and 3.. It's entirely possible to add it, but it would probably...
This doesn't sound like it enables anything that currently isn't possible, it's just new syntax for something that has always been possible.
> This appears to still be an issue on perl 5.30. $. is not set if you do where $f was assigned from *FH{IO} This can also be formulated as...
IMHO it's fine ignore these errors during build, but it's a problem when doing so on release. I think the right default is to make it bail out on `before_release`,...
> The core problem is the fact that I/O functions derive their return code from the filehandle error flag. Instead, they should signal an error only based on the I/O...
The idea of the change sounds like a very good idea, but I can't help wondering if it can't be wired more simply.
If anyone later does need any of the functionality you're leaving out now, can they do that?
> It only limits the APIs declared under PERL_CORE, If we (perl core) need APIs this suppressed we can remove the NO* definition this adds. Yeah then that doesn't matter....