in reply to Re: undefined value as filehandle from Curl.pm
in thread undefined value as filehandle from Curl.pm

That's not the OP's code. That's code in the LWP::Curl module itself: LWP::Curl line 234.

Also, that open should never technically fail, as the file ($content) is declared on the immediate line above. However, it should still be checked, even if out of habit alone, as perhaps corrupt/lack of memory or other oddness can still prevent the open.

Replies are listed 'Best First'.
Re^3: undefined value as filehandle from Curl.pm
by Anonymous Monk on Jun 28, 2016 at 17:36 UTC

    as perhaps corrupt/lack of memory or other oddness can still prevent the open.

    :) if it failed, wouldn't writing to the filehandle fail also?

      Yes, writing to an unopened file handle will result in the run time warning like this: print() on unopened filehandle OUT at C:\Projects_Perl\testing\junk.pl line 11. The code keeps going. Normally what is desired is to "die" when the open fails as something presumably very important didn't happen. If you check the status of the open with an "or die", you also get the line number of where this failure occurred. Try it yourself...
      #!/usr/bin/perl use strict; use warnings; print OUT "something"; print "I kept going"; __END__ Name "main::OUT" used only once: possible typo at C:\Projects_Perl\tes +ting\testopenfailure.pl line 5. print() on unopened filehandle OUT at C:\Projects_Perl\testing\testope +nfailure.pl line 5. I kept going Process completed successfully