Bug #15089 Updated: stat() produces warning instead of error-code.
| From: | herp at wildsau dot idv dot uni-linz dot ac dot at | Date: | Thu, 17 Jan 2002 21:51:46 +0000 |
| Subject: | Bug #15089 Updated: stat() produces warning instead of error-code. | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-77371@lists.php.net to get a copy of this message | ||
ID: 15089
User updated by: herp@wildsau.idv.uni-linz.ac.at
Reported By: herp@wildsau.idv.uni-linz.ac.at
Status: Open
Bug Type: Unknown/Other Function
Operating System: linux
PHP Version: 4.1.1
New Comment:
I used stat() to check the existence of files. If the file I check
does
not
exist, stat() would return FALSE instead of a struct stbuf. This
behaviour is also the *documented* behaviour and is how php-4.0
behaves.
Just 15 mins. ago I installed php-4.1.1. Now, stat() on a
non-existent
file clutters my html-pages with "Warning: file does not exist".
*cough*
Yes, I know that files might not exist, that´s exactly what I use
stat()
for, to check the existance of files. Yes, there is
"file_exists()",
but
why do you output warnings from stat() when returning FALSE is
sufficient? This is one more step away from how one would code
programms in C. Why implement C-like functions (stat(), fstat(),
lstat())
when you have to use other non-obvious functions (file_exists())
to do what you could do with the C-like functions. Stay close to
the
origins.
Now I have to use *two* functions - first I have to use file_exists(),
then I have to use stat(). I am pretty sure that php will execute both
calls using the same system-call, that is, stat(2). That´s suboptimal
and an overhead and a performance penalty (yes I have *many* files). I
just don´t see why the php-engine has to perform the same system-call
twice with exactly the same paramters, when one system-call is enough.
I really think this is not good. And since I am in doubt you will ever
change that, I am considerung switching to mod_perl.
Previous Comments:
------------------------------------------------------------------------
[2002-01-17 16:29:38] herp@wildsau.idv.uni-linz.ac.at
I used stat() to check the existence of files. If the file I check does
not
exist, stat() would return FALSE instead of a struct stbuf. This
behaviour is also the *documented* behaviour and is how php-4.0
behaves.
Just 15 mins. ago I installed php-4.1.1. Now, stat() on a non-existent
file clutters my html-pages with "Warning: file does not exist".
*cough*
Yes, I know that files might not exist, that´s exactly what I use
stat()
for, to check the existance of files. Yes, there is "file_exists()",
but
why do you output warnings from stat() when returning FALSE is
sufficient? This is one more step away from how one would code
programms in C. Why implement C-like functions (stat(), fstat(),
lstat())
when you have to use other non-obvious functions (file_exists())
to do what you could do with the C-like functions. Stay close to the
origins.
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=15089&edit=1