Re: [PHP-DEV] user defined vs php provided function (was Re: str_ireplace vs. stri_replace)
You are correct in the event of a user writing a new function, however consider what will happen if we are dealing with a old code, especially if it is no longer used just by the author but rather by a variety of other people not familiar with PHP code. The result is that after they or their ISPs upgrade to new PHP their scripts will stop working. Couldn't it be solved with just a warning when a function is defined also in user level space and use the user-defined function instead of the one provided by php? Then old systems could work fine, and also the author could notice that a new function is added to php with the same name. I had the same problem before with array_search and was a real pain updating all the sites and sending patches to customers after they installed new version php. Just an idea... Arpi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Register Shutdown Function for Apache
On Thursday 23 January 2003 17:38, Joseph Tate wrote: I can have the patches ready to go in a very short amount of time. I'll work on and post them if I can be reasonably sure they'll be committed. I'm tired of spinning my wheels with this though. I've got a personally patched version of 4.3.0 that will be going into production in a few weeks, so I'm confident in the changes. I'd like to not use a personally patched version of PHP the next time a release comes down the pipe though. +1 on that (if my opinion does matter at all) I'd be very glad if this patch would be in the main release. Thanks for making the fix Joseph! Arpi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] changed behavior of shutdown-registered function in 4.0.x-4.1.x (conn. handling)
On Monday 03 June 2002 18:05, Joseph Tate wrote: Please do not cross post. The register_shutdown_function bug has been open for quite some time: See bug #15209 at http://bugs.php.net/bug.php?id=15209. I work with the original poster, and have access to his patch that seems to fix the problem. I'm working on it today, and hopefully will have a fix soon. Hi Joseph, Thanks for your help. I saw this bug report a few months ago, but couldn't find it now, and thought that maybe it was fixed. I'll try that patch. Thanks, Arpi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] changed behavior of shutdown-registered function in 4.0.x-4.1.x (conn. handling)
Hi, I use register_shutdown_function to regenerate my content-cache's data after the old page were sent. In 4.0.6 there was no problem with it, the connection was closed after the normal script is finished, and before the shutdown_registered function is started (which does the real work). So I could use it for gaining a fake speed in delivering pages, and it really made our system faster because only one process can regenerate the page in a time, the others simply return the old content. But unfortunatelly this doesn't work since 4.1.x, because after the normal script finishes it still holds the line. It doesn't close the connection, so the browser is still waiting for data (and the http process is being held too). Is there any php.ini setting or switch for configure that I can use for turning off this behavior? Or is there any other reason why it works this way for me? If I copy the old (4.0.6) php module over the new one (4.1.1) it works fine. For the dev list: Is there any real reason for this way of connection handling, or it's just a side-effect of some other featuer? Thanks for your help, Arpi p.s.:sorry for mailing this to the dev list too, but I don't know where can I find somebody who can help -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
