In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/95032a5ba8a8a8ef02ca87ced5e2e47387c05831?hp=15daaef1c6ad780d2bd6b197bf9fda7408acb22e>
- Log ----------------------------------------------------------------- commit 95032a5ba8a8a8ef02ca87ced5e2e47387c05831 Author: Aristotle Pagaltzis <[email protected]> Date: Sat Mar 26 00:55:21 2016 +0100 improve perldiag implicit close text still further ----------------------------------------------------------------------- Summary of changes: pod/perldiag.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pod/perldiag.pod b/pod/perldiag.pod index 32be458..777226f 100644 --- a/pod/perldiag.pod +++ b/pod/perldiag.pod @@ -7109,10 +7109,10 @@ when its reference count reached zero while it was still open, e.g.: print $fh $data or die "print: $!"; } # implicit close here -Various errors may only be detected when a filehandle is closed, e.g. buffering -may allow the C<print> in this example to succeed even though the disk is full, -and this makes it necessary to check the result of a close(). So when the close() -is implicit, perl will signal errors by warning. +Because various errors may only be detected by close() (e.g. buffering could +allow the C<print> in this example to return true even when the disk is full), +it is dangerous to ignore its result. So when it happens implicitly, perl will +signal errors by warning. B<Prior to version 5.22.0, perl ignored such errors>, so the common idiom shown above was liable to cause B<silent data loss>. -- Perl5 Master Repository
