[PHP-DEV] Bug #15032 Updated: Date_Calc::getMonthFullName() problem
ID: 15032 Updated by: yavo Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: PEAR related Operating System: Linux PHP Version: 4.0.6 Previous Comments: [2002-01-14 13:18:59] [EMAIL PROTECTED] For the getMonthFullName function the specs state the input should be in the form MM. If call the function with 01 as its input it works fine. I believe php is automatically casting the number to an int and thus removing the 0. However, there are some cases where the function is called with a variable as input (in my case a get variable) where this casting does not occur. The function then returns nothing. Below is a diff that fixes the getMonthFullName and GetMonthAbbrName for this case. File bug.php: ? require 'Date/Calc.php'; $en_month = Date_Calc::getMonthFullname($month); echo Test $en_month; ? bug.php?month=01 output: Before patch: Test After patch: Test January 1434c1434,1436 --- // Cast month to an int to eliminate starting zero $month = (int)$month; 1457a1460 $month = (int)$month; Edit this bug report at http://bugs.php.net/?id=15032edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15032 Updated: Date_Calc::getMonthFullName() problem
ID: 15032 Updated by: yavo Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: PEAR related Operating System: Linux PHP Version: 4.0.6 Previous Comments: [2002-01-14 13:18:59] [EMAIL PROTECTED] For the getMonthFullName function the specs state the input should be in the form MM. If call the function with 01 as its input it works fine. I believe php is automatically casting the number to an int and thus removing the 0. However, there are some cases where the function is called with a variable as input (in my case a get variable) where this casting does not occur. The function then returns nothing. Below is a diff that fixes the getMonthFullName and GetMonthAbbrName for this case. File bug.php: ? require 'Date/Calc.php'; $en_month = Date_Calc::getMonthFullname($month); echo Test $en_month; ? bug.php?month=01 output: Before patch: Test After patch: Test January 1434c1434,1436 --- // Cast month to an int to eliminate starting zero $month = (int)$month; 1457a1460 $month = (int)$month; Edit this bug report at http://bugs.php.net/?id=15032edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15032 Updated: Date_Calc::getMonthFullName() problem
ID: 15032 Updated by: yavo Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: PEAR related Operating System: Linux PHP Version: 4.0.6 Previous Comments: [2002-01-14 13:18:59] [EMAIL PROTECTED] For the getMonthFullName function the specs state the input should be in the form MM. If call the function with 01 as its input it works fine. I believe php is automatically casting the number to an int and thus removing the 0. However, there are some cases where the function is called with a variable as input (in my case a get variable) where this casting does not occur. The function then returns nothing. Below is a diff that fixes the getMonthFullName and GetMonthAbbrName for this case. File bug.php: ? require 'Date/Calc.php'; $en_month = Date_Calc::getMonthFullname($month); echo Test $en_month; ? bug.php?month=01 output: Before patch: Test After patch: Test January 1434c1434,1436 --- // Cast month to an int to eliminate starting zero $month = (int)$month; 1457a1460 $month = (int)$month; Edit this bug report at http://bugs.php.net/?id=15032edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PEAR-DEV] PHP and WebDAV
The immediately most useful stuff for PHP would be server functionality in cooperation with mod_dav. The client part seems to be much easier to implement. Both Rasmus and I fell off this project as you can see, so if someone want to pick it up, that'd be awesome. - Stig If I'm not terribly mistaken WebDav requires some sort of a HTTP server to work. I started writing a HTTP::Server module recently. I wanted it so I could provide XMLPRC interface for Pear enabled sites. Any way the idea is to write a very basic HTTP server for PEAR (using the socket extension) and make it extendable so it would be easy inherit it and overwrite some methods and make it work as a proxy for XMLRPC. Maybe this could also be used for WebDav. For all those who are going to say that it's gona have lousy performance I know Yavor -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] oci hell.
On several occasions I had to install php with oci8 on redhat Linux (6.2) with different versions of apache 1.12 - 1.17 with Oracle 8.1.6 client . Every single time I get the same thing. Apache shows no errors, the apache start script shows no errors but dies without an error. This only happens when the oci8 extension is enabled.I've tried anything I could. I've put the oracle variables in any place I could think of (except one) in the environment rc files, in httpd.conf file with SetEnv directives and in the apachestl file. The variables I export are ORACLE_HOME LD_LIBRARY_PATH and ORACLE_SID . Can someone tell me what condition would cause oci8 to die. I'm I doing something wrong. It's been many hours and I'm getting frustrated. I've tried the following things Oracle Client 8.1.3 + Apache 1.17 | Apache 1.19 + Php 4.0.4pl1 | Php 4.0.3pl1 Oracle Client 8.1.2 + Apache 1.14-5 (comes with RedHat 6.2) | Apache 1.19 + Php 4.0.4pl1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] PHP 4.0 Bug #9664: Unable to make , related to bug 8468 i think
From: [EMAIL PROTECTED] Operating system: Solaris 8 PHP version: 4.0.4 PHP Bug Type: Sockets related Bug description: Unable to make , related to bug 8468 i think My enviroment Solaris 8 Gnu gcc compile options ./configure --enable-sockets This bug occured to some one and he asked me to look in to it. I tried it on another machine same enviroment and got the same problem. A search revealed a similar ( i think ) bug with id 8468 . This is the dump of the error. Making all in sockets gcc -I. -I/people/yavo/work/php-4.0.4/ext/sockets -I/people/yavo/work/php-4.0.4/main -I/people/yavo/work/php-4.0.4 -I/people/yavo/work/php-4.0.4/Zend -I/people/yavo/work/php-4.0.4/ext/mysql/libmysql -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmltok -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmlparse -I/people/yavo/work/php-4.0.4/TSRM -D_POSIX_PTHREAD_SEMANTICS -DXML_BYTE_ORDER=12 -g -O2 -c sockets.c touch sockets.lo sockets.c:118: `php_if___xnet_listen' undeclared here (not in a function) sockets.c:118: initializer element is not constant sockets.c:118: (near initialization for `sockets_functions[10].handler') sockets.c:139: `php_if___xnet_socket' undeclared here (not in a function) sockets.c:139: initializer element is not constant sockets.c:139: (near initialization for `sockets_functions[16].handler') sockets.c:140: `php_if___xnet_connect' undeclared here (not in a function) sockets.c:140: initializer element is not constant sockets.c:140: (near initialization for `sockets_functions[17].handler') sockets.c:142: `php_if___xnet_bind' undeclared here (not in a function) sockets.c:142: initializer element is not constant sockets.c:142: (near initialization for `sockets_functions[19].handler') sockets.c:146: `php_if___xnet_sendto' undeclared here (not in a function) sockets.c:146: initializer element is not constant sockets.c:146: (near initialization for `sockets_functions[23].handler') sockets.c:153: `php_if___xnet_recvmsg' undeclared here (not in a function) sockets.c:153: initializer element is not constant sockets.c:153: (near initialization for `sockets_functions[30].handler') sockets.c:154: `php_if___xnet_sendmsg' undeclared here (not in a function) sockets.c:154: initializer element is not constant sockets.c:154: (near initialization for `sockets_functions[31].handler') sockets.c:157: `php_if___xnet_getsockopt' undeclared here (not in a function) sockets.c:157: initializer element is not constant sockets.c:157: (near initialization for `sockets_functions[34].handler') sockets.c:159: `php_if___xnet_socketpair' undeclared here (not in a function) sockets.c:159: initializer element is not constant sockets.c:159: (near initialization for `sockets_functions[36].handler') *** Error code 1 make: Fatal error: Command failed for target `sockets.lo' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext *** Error code 1 make: Fatal error: Command failed for target `all-recursive' [yavo@crayxmp php-4.0.4]$ -- Edit Bug report at: http://bugs.php.net/?id=9664edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] PHP 4.0 Bug #9664 Updated: Unable to make , related to bug 8468 i think
ID: 9664 User Update by: [EMAIL PROTECTED] Old-Status: Feedback Status: Open Bug Type: Sockets related Description: Unable to make , related to bug 8468 i think Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo Previous Comments: --- [2001-03-09 18:46:22] [EMAIL PROTECTED] Please try the latest CVS snapshot from http://snaps.php.net/ as there have been some fixes for this. --Jani --- [2001-03-09 16:24:19] [EMAIL PROTECTED] My enviroment Solaris 8 Gnu gcc compile options ./configure --enable-sockets This bug occured to some one and he asked me to look in to it. I tried it on another machine same enviroment and got the same problem. A search revealed a similar ( i think ) bug with id 8468 . This is the dump of the error. Making all in sockets gcc -I. -I/people/yavo/work/php-4.0.4/ext/sockets -I/people/yavo/work/php-4.0.4/main -I/people/yavo/work/php-4.0.4 -I/people/yavo/work/php-4.0.4/Zend -I/people/yavo/work/php-4.0.4/ext/mysql/libmysql -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmltok -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmlparse -I/people/yavo/work/php-4.0.4/TSRM -D_POSIX_PTHREAD_SEMANTICS -DXML_BYTE_ORDER=12 -g -O2 -c sockets.c touch sockets.lo sockets.c:118: `php_if___xnet_listen' undeclared here (not in a function) sockets.c:118: initializer element is not constant sockets.c:118: (near initialization for `sockets_functions[10].handler') sockets.c:139: `php_if___xnet_socket' undeclared here (not in a function) sockets.c:139: initializer element is not constant sockets.c:139: (near initialization for `sockets_functions[16].handler') sockets.c:140: `php_if___xnet_connect' undeclared here (not in a function) sockets.c:140: initializer element is not constant sockets.c:140: (near initialization for `sockets_functions[17].handler') sockets.c:142: `php_if___xnet_bind' undeclared here (not in a function) sockets.c:142: initializer element is not constant sockets.c:142: (near initialization for `sockets_functions[19].handler') sockets.c:146: `php_if___xnet_sendto' undeclared here (not in a function) sockets.c:146: initializer element is not constant sockets.c:146: (near initialization for `sockets_functions[23].handler') sockets.c:153: `php_if___xnet_recvmsg' undeclared here (not in a function) sockets.c:153: initializer element is not constant sockets.c:153: (near initialization for `sockets_functions[30].handler') sockets.c:154: `php_if___xnet_sendmsg' undeclared here (not in a function) sockets.c:154: initializer element is not constant sockets.c:154: (near initialization for `sockets_functions[31].handler') sockets.c:157: `php_if___xnet_getsockopt' undeclared here (not in a function) sockets.c:157: initializer element is not constant sockets.c:157: (near initialization for `sockets_functions[34].handler') sockets.c:159: `php_if___xnet_socketpair' undeclared here (not in a function) sockets.c:159: initializer element is not constant sockets.c:159: (near initialization for `sockets_functions[36].handler') *** Error code 1 make: Fatal error: Command failed for target `sockets.lo' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext *** Error code 1 make: Fatal error: Command failed for target `all-recursive' [yavo@crayxmp php-4.0.4]$ --- Full Bug description available at: http://bugs.php.net/?id=9664 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] PHP 4.0 Bug #9664 Updated: Unable to make , related to bug 8468 i think
ID: 9664 User Update by: [EMAIL PROTECTED] Status: Open Bug Type: Sockets related Description: Unable to make , related to bug 8468 i think Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo Previous Comments: --- [2001-03-09 19:28:59] [EMAIL PROTECTED] Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo --- [2001-03-09 18:46:22] [EMAIL PROTECTED] Please try the latest CVS snapshot from http://snaps.php.net/ as there have been some fixes for this. --Jani --- [2001-03-09 16:24:19] [EMAIL PROTECTED] My enviroment Solaris 8 Gnu gcc compile options ./configure --enable-sockets This bug occured to some one and he asked me to look in to it. I tried it on another machine same enviroment and got the same problem. A search revealed a similar ( i think ) bug with id 8468 . This is the dump of the error. Making all in sockets gcc -I. -I/people/yavo/work/php-4.0.4/ext/sockets -I/people/yavo/work/php-4.0.4/main -I/people/yavo/work/php-4.0.4 -I/people/yavo/work/php-4.0.4/Zend -I/people/yavo/work/php-4.0.4/ext/mysql/libmysql -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmltok -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmlparse -I/people/yavo/work/php-4.0.4/TSRM -D_POSIX_PTHREAD_SEMANTICS -DXML_BYTE_ORDER=12 -g -O2 -c sockets.c touch sockets.lo sockets.c:118: `php_if___xnet_listen' undeclared here (not in a function) sockets.c:118: initializer element is not constant sockets.c:118: (near initialization for `sockets_functions[10].handler') sockets.c:139: `php_if___xnet_socket' undeclared here (not in a function) sockets.c:139: initializer element is not constant sockets.c:139: (near initialization for `sockets_functions[16].handler') sockets.c:140: `php_if___xnet_connect' undeclared here (not in a function) sockets.c:140: initializer element is not constant sockets.c:140: (near initialization for `sockets_functions[17].handler') sockets.c:142: `php_if___xnet_bind' undeclared here (not in a function) sockets.c:142: initializer element is not constant sockets.c:142: (near initialization for `sockets_functions[19].handler') sockets.c:146: `php_if___xnet_sendto' undeclared here (not in a function) sockets.c:146: initializer element is not constant sockets.c:146: (near initialization for `sockets_functions[23].handler') sockets.c:153: `php_if___xnet_recvmsg' undeclared here (not in a function) sockets.c:153: initializer element is not constant sockets.c:153: (near initialization for `sockets_functions[30].handler') sockets.c:154: `php_if___xnet_sendmsg' undeclared here (not in a function) sockets.c:154: initializer element is not constant sockets.c:154: (near initialization for `sockets_functions[31].handler') sockets.c:157: `php_if___xnet_getsockopt' undeclared here (not in a function) sockets.c:157: initializer element is not constant sockets.c:157: (near initialization for `sockets_functions[34].handler') sockets.c:159: `php_if___xnet_socketpair' undeclared here (not in a function) sockets.c:159: initializer element is not constant sockets.c:159: (near initialization for `sockets_functions[36].handler') *** Error code 1 make: Fatal error: Command failed for target `sockets.lo' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext *** Error code 1 make: Fatal error: Command failed for target `all-recursive' [yavo@crayxmp php-4.0.4]$ --- Full Bug description available at: http://bugs.php.net/?id=9664 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] PHP 4.0 Bug #9664 Updated: Unable to make , related to bug 8468 i think
ID: 9664 User Update by: [EMAIL PROTECTED] Old-Status: Feedback Status: Open Bug Type: Sockets related Description: Unable to make , related to bug 8468 i think Ok I'really hate to be a nag, but just finished compiling the latest cvs snapshot, it's still the same error. I wonder if im missing a library. Which libs does the socket extention use. BTW Thanks for your so imadiate response. -- yavo Previous Comments: --- [2001-03-09 20:10:58] [EMAIL PROTECTED] Yes, you should try with the whole CVS snapshot and not try to replace any files from it in PHP 4.0.4. --Jani --- [2001-03-09 19:29:22] [EMAIL PROTECTED] Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo --- [2001-03-09 19:28:59] [EMAIL PROTECTED] Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo --- [2001-03-09 18:46:22] [EMAIL PROTECTED] Please try the latest CVS snapshot from http://snaps.php.net/ as there have been some fixes for this. --Jani --- [2001-03-09 16:24:19] [EMAIL PROTECTED] My enviroment Solaris 8 Gnu gcc compile options ./configure --enable-sockets This bug occured to some one and he asked me to look in to it. I tried it on another machine same enviroment and got the same problem. A search revealed a similar ( i think ) bug with id 8468 . This is the dump of the error. Making all in sockets gcc -I. -I/people/yavo/work/php-4.0.4/ext/sockets -I/people/yavo/work/php-4.0.4/main -I/people/yavo/work/php-4.0.4 -I/people/yavo/work/php-4.0.4/Zend -I/people/yavo/work/php-4.0.4/ext/mysql/libmysql -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmltok -I/people/yavo/work/php-4.0.4/ext/xml/expat/xmlparse -I/people/yavo/work/php-4.0.4/TSRM -D_POSIX_PTHREAD_SEMANTICS -DXML_BYTE_ORDER=12 -g -O2 -c sockets.c touch sockets.lo sockets.c:118: `php_if___xnet_listen' undeclared here (not in a function) sockets.c:118: initializer element is not constant sockets.c:118: (near initialization for `sockets_functions[10].handler') sockets.c:139: `php_if___xnet_socket' undeclared here (not in a function) sockets.c:139: initializer element is not constant sockets.c:139: (near initialization for `sockets_functions[16].handler') sockets.c:140: `php_if___xnet_connect' undeclared here (not in a function) sockets.c:140: initializer element is not constant sockets.c:140: (near initialization for `sockets_functions[17].handler') sockets.c:142: `php_if___xnet_bind' undeclared here (not in a function) sockets.c:142: initializer element is not constant sockets.c:142: (near initialization for `sockets_functions[19].handler') sockets.c:146: `php_if___xnet_sendto' undeclared here (not in a function) sockets.c:146: initializer element is not constant sockets.c:146: (near initialization for `sockets_functions[23].handler') sockets.c:153: `php_if___xnet_recvmsg' undeclared here (not in a function) sockets.c:153: initializer element is not constant sockets.c:153: (near initialization for `sockets_functions[30].handler') sockets.c:154: `php_if___xnet_sendmsg' undeclared here (not in a function) sockets.c:154: initializer element is not constant sockets.c:154: (near initialization for `sockets_functions[31].handler') sockets.c:157: `php_if___xnet_getsockopt' undeclared here (not in a function) sockets.c:157: initializer element is not constant sockets.c:157: (near initialization for `sockets_functions[34].handler') sockets.c:159: `php_if___xnet_socketpair' undeclared here (not in a function) sockets.c:159: initializer element is not constant sockets.c:159: (near initialization for `sockets_functions[36].handler') *** Error code 1 make: Fatal error: Command failed for target `sockets.lo' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /people/yavo/work/php-4.0.4/ext/sockets *** Error code 1 make: Fatal error: Command
[PHP-DEV] PHP 4.0 Bug #9664 Updated: Unable to make , related to bug 8468 i think
ID: 9664 User Update by: [EMAIL PROTECTED] Status: Open Bug Type: Sockets related Description: Unable to make , related to bug 8468 i think No but it's my understanding that this (SOlaris Workishop CC) is a commersial product which you have to buy from solaris. I'm right. -- yavor Previous Comments: --- [2001-03-09 20:47:37] [EMAIL PROTECTED] Ok I'really hate to be a nag, but just finished compiling the latest cvs snapshot, it's still the same error. I wonder if im missing a library. Which libs does the socket extention use. BTW Thanks for your so imadiate response. -- yavo --- [2001-03-09 20:24:07] [EMAIL PROTECTED] You're not missing any libraries..FYI: The sockets extension is still EXPERIMENTAL, ie. it's not very stable yet. This is yet another bug in it. Have you tried compiling it with the Solaris Workshop CC ??? --Jani --- [2001-03-09 20:16:31] [EMAIL PROTECTED] Ok I'really hate to be a nag, but just finished compiling the latest cvs snapshot, it's still the same error. I wonder if im missing a library. Which libs does the socket extention use. BTW Thanks for your so imadiate response. -- yavo --- [2001-03-09 20:10:58] [EMAIL PROTECTED] Yes, you should try with the whole CVS snapshot and not try to replace any files from it in PHP 4.0.4. --Jani --- [2001-03-09 19:29:22] [EMAIL PROTECTED] Hi Jani, Prior to submiting this bug I tried two things first I applied the pathch in bug 8468, next I got the latest cvs snapshot as of 5-6 hours before this post and replased all files in the ext/sockets dir with the files from the snapshot. As this is clearly a socket extention problem I didn't replace any other files. Do you thinkit would make any sence to replace any other files. -- yavo --- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. Full Bug description available at: http://bugs.php.net/?id=9664 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] PHP 4.0 Bug #8674: invallid filetype() results (affects isdir() )
From: [EMAIL PROTECTED]
Operating system: redhat 6.2
PHP version: 4.0.4
PHP Bug Type: Filesystem function related
Bug description: invallid filetype() results (affects isdir() )
im using php for shell scripting in redhat 6.2. compiled with
'./configure' '--with-apxs=/usr/local/apache/bin/apxs' '--with-oci8=/usr/local/oracle'
trying to get the filetype files returns null for all entries exsept . and .. .
-- code snippet --
$dp = opendir($dir);
if($dp){
while (($file = readdir($dp))!== false) {
// Skip . and .. and check for type
// tried with this on and both here and at the start
clearstatcache();
print($file." - ".filetype($file)."\n");
if(($file != ".") ($file != "..") (filetype($file) == $type)){
$files[] = $file;
}
}//while
return($files);
}//if
else{
debug("The directory [$dir] was not found or couldn't be opened");
write_log("The directory [$dir] was not found or couldn't be opened");
return(0);
}
-- end of snippet -
--
Edit Bug report at: http://bugs.php.net/?id=8674edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
