Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
PHP Programming

PHP 4.3.6 Released 34

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."
This discussion has been archived. No new comments can be posted.

PHP 4.3.6 Released

Comments Filter:
  • Please mod this up.
  • ... I know I have read somewhere about some rather nasty bugs that are still not fixed in this version.
    Anyone know anything more about this?
  • Compile 64bit? (Score:4, Interesting)

    by Rtsbasic ( 709532 ) on Friday April 16, 2004 @09:21AM (#8880075) Journal
    Does this mean PHP will compile as 64bit code now?
    "Fixed bug #27717 (Test Failures when compiled on 64-bit mode)"
    • Compiling PHP on a 64bit platform worked since some times. As you can see at bug #27717 [php.net] make test, after compiling failed at some tests, which work now. I know some 64bit isntallations even though I haven't such a machine myself....
  • Threaded environment (Score:3, Interesting)

    by Anonymous Coward on Friday April 16, 2004 @09:33AM (#8880176)

    It's not just Windows that can be threaded environments, FreeBSD and Linux also have the option of using the per-child MPM.

    • FreeBSD and Linux also have the option of using the per-child MPM

      According to the Apache docs, perchild MPM does not work. Using FastCGI PHP will likely have much better results. PHP has always had problems with thread safety.
      • by Anonymous Coward
        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'
        • 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.
  • So does this mean Apache 2.0 will now play nicer with PHP?
    • To those struggling, just use FastCGI; it'll perform just as well if not better, it'll easily halve the size of your httpd's, and it neatly circumvents any collisions with your favourite MPM.

    • We've been using mod_php (PHP 4.3.4) and Apache 2 on SemWebCentral [semwebcentral.org] for a while now with no problems...

      * fingers crossed *
    • What problems are you experiencing with PHP under Apache 2.0? I've been using the two together successfully with no problems on several non-production boxes, and haven't seen any problems which would lead me to believe that I shouldn't use them on production boxen. Are the issues with apache 2.0 and php relatively isolated?
  • thread bugs (Score:3, Funny)

    by Anonymous Coward on Friday April 16, 2004 @11:34AM (#8881381)
    Oh please, PHP can't handle threads properly. Yet another reason to switch to Per-- oh wait, threads? Nevermind.
    • Serious question: are there any open source scripting languages that _can_ handle threads?
      • Serious question: are there any open source scripting languages that _can_ handle threads?

        Python has full thread support.
      • Serious question: are there any open source scripting languages that _can_ handle threads?

        PHP itself is completly thread safe, but as soon as you link it to a library, that is not threadsafe PHP isn't thread safe anymore and usually you link PHP against many libs (glibc, gd, libxml2, mysql, ldap, ...) and some of them aren't thread safe. Just configure PHP with something like

        ./configure --disable-all --with-apache2

        and you've got an threadsafe PHP build for Apache2 - but using this isn't any fun since

  • It is nice with another bugfix release, but what I'm really looking forward to is the release of PHP 5 with Zend Engine 2.0 [php.net]. Then the object model will finally be sane (private/protected member variables for example).
    • Re:PHP 5 (Score:4, Interesting)

      by JoScherl ( 228091 ) on Saturday April 17, 2004 @03:17PM (#8892924) Homepage

      I think you don't really need public/private/protected in a scripting language. More interesting for me are other improvements like that assignments like

      $a = new foo();
      $b =$a;

      are made by reference. With PHP4 even the first line would create a copy of the object. Also interesting arenew extensions like MySLi [php.net], the new soap extension [php.net] or the rewrite of the XML-Extensin based on libxml2 (including the realy nice SimpleXML-Extension [php.net]) ....

      A collection of PHP5 information can be found p.e. on this German site [phpbar.de] (most links lead to English pages, and I'm one of the ones running this site - so it's the best (German) PHP site *g*)

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...