Re: RE: [PHP-DOC] #20822 [Com]: getimagesize() returning null instead of false
| From: | Rick Widmer | Date: | Thu, 05 Dec 2002 21:50:19 +0000 |
| Subject: | Re: RE: [PHP-DOC] #20822 [Com]: getimagesize() returning null instead of false | ||
| References: | 1 | Groups: | php.dev php.doc |
| Request: | Send a blank email to php-dev+get-92143@lists.php.net to get a copy of this message | ||
At 03:02 PM 12/5/02 +0100, Tit \"Black\" Petric wrote:
If you don't want to see the filesystem error use @ to hide them. Having filesystem errors available makes troubleshooting easier. If GetImageSize never returns them, how do you figure out what is wrong when you it returns false? RickFrom my point of view accessing a file should result in an error if the file cannot be opened or in case of GetImageSize() a file operation cannot be executed. For example i would expect GetImageSize() to show an error if the information cannot be retrieved due to file corruptions.I agree. Absolutely. Masking bona fide file operation errors would be a huge mistake, IMHO. I personally dissagree here - an error is a bit harsh if it doesn't hinder execution - I dont see anything in getimagesize() which should return E_ERROR - only E_NOTICE if the file is corrupt, unless I'm missing something.