Suggested Slogan:
PHP: Now with close to 400 lines of configure options...
--
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]
Sadly they made this change. I don't agree with it or like it, but the
change has been made. Use exists instead.
--
Mike
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 11, 2001 9:22 AM
Subject: [PHP-DEV] Bug #14424: is_readable returns error
This has been changed. Use exists() first. Technically, if the file does
exist, it's not a file in my opinion and should return false, but nobody
seems to agree with me.
--
Mike
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 11, 2001 5:01 AM
Agreed.
These changes should be made into toggles. If you ask me, if the file
doesn't exist, it's not a file. That shouldn't be an error message.
--
Mike
- Original Message -
From: Vitali Evstigneev [EMAIL PROTECTED]
To: Mike Rogers [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent
There was some question of this quite some time ago.
is_file() was changed (to many peoples annoyance by what I saw) to
report the error.
file_exists still shouldn't report the error. Personally, I think they
both shouldn't. If it doesn't exist, it sure as hell isn't a file, so it
Because that appears to be rediculous idea. At present, unless you have a
problem which requires you to upgrade, you stick with the stable proven
release. The only reason why Linux kernel gets released so often is because
it contains security fixes that affect everyone and are in the public.
Does this memlimit patch need to be applied to 4.0.8-dev or 4.1.0 builds, or
has it been finally implemented into the distribution
--
Mike
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 21, 2001 1:20 AM
Subject: [PHP-DEV] Bug #12068 Updated:
Guys;
Is there any way to get the Zend Optimizer to work with the latest CVS
snapshot. I really need it working and can't go backwards because I would
break why I am using a snapshot in the first place.
Any ideas?
--
Mike
--
PHP Development Mailing List http://www.php.net/
To
Guys- How about we add the current development version (4.1.0RC1) to the
bug-track database's lists of options. It would make a lot of sense if
people aren't filling out 4.1.0RC1 bugs claiming them to be 4.0.6 bugs.
--
Mike
--
PHP Development Mailing List http://www.php.net/
To unsubscribe,
mysql_num_rows() to a result that returned zero rows returns 'Supplied
argument is not a valid MySQL result resource'. If it is an invalid
resource (such as SELECT * from table to an empty table), shouldn't it
return ZERO (0).
That seems to make the most sense, as opposed to throwing
Ignore.
This only happened for a few minutes and without changing anything
started working. I don't know why.
--
Mike
- Original Message -
From: Mike Rogers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 30, 2001 12:48 AM
Subject: [PHP-DEV] MySQL_Num_Rows
I have just upgraded to the new PostgreSQL 7.1.3 (from 7.0.3) and have been
experiencing a pretty serious problem:
On one particular page, in what seems to be completely random instances,
I get buffer overruns and either 0-rows or a crashed apache child. Turning
on PHP's --enable-debug, I
: Zeev Suraski [EMAIL PROTECTED]
To: Mike Rogers [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, September 26, 2001 6:51 PM
Subject: Re: [PHP-DEV] PostgreSQL / PHP Overrun Error
Can you try the latest CVS? It should fix the problem.
Zeev
At 18:35 26-09-01, Mike
I have tried setting as follows in my .htaccess and in my apache server
logs:
php_value error_log /path/to/log.file
php_flag log_errors On
And it doesn't seem to do anything. I am already logging to each virtual
hosts' error log for http-related logs [such as not found, etc].
setup with ease.
--
Mike
- Original Message -
From: Zeev Suraski [EMAIL PROTECTED]
To: Mike Rogers [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 26, 2001 9:21 PM
Subject: Re: [PHP-DEV] PostgreSQL / PHP Overrun Error
4.0.7 will include this fix. All I can say
I seem to have found a leak:
php_smart_str.h(74) : Freeing 0x08641FF4 (4568 bytes),
script=/path/to/file.php
Last leak repeated 2 times
Latest CVS (9.45pm EST, Wednesday night)
--
Mike
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
for
it to come up if that would help.
--
Mike
- Original Message -
From: Sterling Hughes [EMAIL PROTECTED]
To: Mike Rogers [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 26, 2001 10:57 PM
Subject: Re: [PHP-DEV] php_smart_str leek
On Wed, 26 Sep 2001, Mike Rogers wrote:
I
17 matches
Mail list logo
