Slashdot Mirror

← Back to Stories (view on slashdot.org)

PHP 4.3.6 Released

Posted by michael on from the hyped-up-on-php dept.

ehmdjii writes "The PHP Development Team is proud to announce the release of PHP 4.3.6. This is is a bug fix release whose primary goal is to address two bugs which may result in crashes in PHP builds with thread-safety enabled. All users of PHP in a threaded environment (Windows) are strongly encouraged to upgrade to this release. All in all this release fixes approximately 25 bugs that have been discovered since the 4.3.5 release. For a full list of changes in PHP 4.3.6, see the ChangeLog."

6 of 34 comments (clear)

  1. Re:NO MORE PHP! by yelvington · · Score: 4, Insightful

    If anyone is forcing you to entangle content, presentation and business logic, dial 911.

    Try some self-discipline. It's not the language's fault.

  2. Re:NO MORE PHP! by Anonymous Coward · · Score: 1, Insightful

    Sorry, but that's what PHP is for.

    If you're not entangling your content, presentation and logic with PHP, then you're wasting time and should have chosen something better :)

  3. Re:NO MORE PHP! by Anonymous Coward · · Score: 1, Insightful

    PHP's not exactly a stunner when it comes to performance, especially when comparing with a well written Java application on a good JVM.

  4. Re:NO MORE PHP! by Anonymous Coward · · Score: 1, Insightful

    Have you actually tried running a servlet? Do you know how well they perform, or are you just spouting out rubbish about Java being slow because you used a bad Swing app 3 years ago?

    Oh yeah, Java makes it pretty trivial to cache content too.

  5. Re:Threaded environment by Anonymous Coward · · Score: 2, Insightful

    You mean UNIX has always had problems with thread safety. It's not really PHP that is the issue here, it is the large number of libraries that can be compiled into PHP. For example, the very common gdbm library is not threadsafe. And for the longest time the PostgreSQL client library was "mostly" threadsafe except if you happened to use crypt() in a query. Or how about the c-client library? Blaming PHP for not solving problems in 3rd-party libraries is not really fair. A generic PHP script that doesn't touch any troublesome third-party libraries will run just fine in a threaded environment.

  6. Re:Threaded environment by Electrum · · Score: 2, Insightful

    Blaming PHP for not solving problems in 3rd-party libraries is not really fair.

    You are correct that PHP's thread safety issues (most likely) lie with third party libraries. However, PHP could fix most of the problems by using mutexes around the unsafe library calls.