From 4d383607e45d2ed8b044662e85b1f5e1d8825d77 Mon Sep 17 00:00:00 2001 From: jkeenan Date: Mon, 27 Feb 2012 12:34:10 -0500 Subject: Explain why program must close __DATA__ handle. Adapted from suggestion by David Golden++. For RT #37033. --- pod/perldata.pod | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/pod/perldata.pod b/pod/perldata.pod index 16ceb41048..4322af9013 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -416,12 +416,13 @@ end of file. Any following text is ignored. Text after __DATA__ may be read via the filehandle C, where C is the package that was current when the __DATA__ token was encountered. The filehandle is left open pointing to the -line after __DATA__. It is the program's responsibility to -C when it is done reading from it. For compatibility with -older scripts written before __DATA__ was introduced, __END__ behaves -like __DATA__ in the top level script (but not in files loaded with -C or C) and leaves the remaining contents of the -file accessible via C. +line after __DATA__. The program should C when it is done +reading from it. (Leaving it open leaks filehandles if the module is +reloaded for any reason, so it's a safer practice to close it.) For +compatibility with older scripts written before __DATA__ was +introduced, __END__ behaves like __DATA__ in the top level script (but +not in files loaded with C or C) and leaves the remaining +contents of the file accessible via C. See L for more description of __DATA__, and an example of its use. Note that you cannot read from the DATA -- cgit v1.2.1