PHP 4.3.0 Released

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Scott MacVicar
    Former vBulletin Developer
    • Dec 2000
    • 13286

    PHP 4.3.0 Released



    PHP 4.3.0 Release Announcement

    After a long and arduous 8 months of development and testing, PHP 4.3.0 is out! With regard to scope, time, and effort, this is the largest 4.x release of PHP, and it further elevates PHP's standing as a serious contender in the general purpose scripting language arena.
    Command line interface

    This version finalizes the separate command line interface (CLI) that can be used for developing shell and desktop applications (with PHP-GTK). The CLI is always built, but installed automatically only if CGI version is disabled via --disable-cgi switch during configuration. Alternatively, one can use make install-cli target. On Windows CLI can be found in cli folder.
    CLI has a number of differences compared to other server APIs. More information can be found here:
    Streams

    A very important "under the hood" feature is the streams API. It introduces a unified approach to the handling of files, pipes, sockets, and other I/O resources in the PHP core and extensions.
    What this means for users is that any I/O function that works with streams (and that is almost all of them) can access built-in protocols, such as HTTP/HTTPS and FTP/FTPS, as well as custom protocols registered from PHP scripts. For more information please see:
    New build system

    This iteration of the build system, among other things, replaces the slow recursive make with one global Makefile and eases the integration of proper dependencies. Automake is only needed for its aclocal tool. The build process is now more portable and less resource-consuming.
    Improvements

    PHP 4.3.0 has many improvements and enhancements:
    • GD library is now bundled with the distribution and it is recommended to always use the bundled version
    • vpopmail and cybermut extensions are moved to PECL
    • several deprecated extensions (aspell, ccvs, cybercash, icap) and SAPIs (fastcgi, fhttpd) are removed
    • speed improvements in a variety of string functions
    • Apache2 filter is improved, but is still considered experimental (use with PHP in prefork and not worker (thread) model since many extensions based on external libraries are not thread safe)
    • various security fixes (imap, mysql, mcrypt, file upload, gd, etc)
    • new SAPI for embedding PHP in other applications (experimental)
    • much better test suite
    • significant improvements in dba, gd, pcntl, sybase, and xslt extensions
    • debug_backtrace() should help with debugging
    • error messages now contain URLs linking to pages describing the error or function in question
    • Zend Engine has some fixes and minor performance enhancements
    • and TONS of other fixes, updates, new functions, etc
    For the full list of changes in PHP 4.3.0, see the ChangeLog file.
    Scott MacVicar

    My Blog | Twitter
  • Cyborg from DH
    Senior Member
    • Nov 2002
    • 305

    #2
    Been using 4.3.0 since Pre2, working great, except for a bug RC2 had, which they fixed in RC3.

    Final version looks great, and should work wonderfully.

    Comment

    • nuno
      Senior Member
      • Apr 2001
      • 4346
      • 3.8.x

      #3
      Thanks Scott
      You're my Prince of Peace
      And I will live my life for You

      Comment

      • waddy
        Member
        • Feb 2002
        • 97
        • 2.3.2

        #4
        Thanks for the heads up Scott.

        Is that damn mbstring bug fixed in this release, i couldnt find any mention ?

        Has anyone been game enough to upgrade yet, if so, any news ?

        Comment

        • nuno
          Senior Member
          • Apr 2001
          • 4346
          • 3.8.x

          #5
          Dang, what happened to the Zend Engine 2?
          It was released with 4.3.0-dev, it should be packed with 4.3.0 final IMO.
          You're my Prince of Peace
          And I will live my life for You

          Comment

          • Scott MacVicar
            Former vBulletin Developer
            • Dec 2000
            • 13286

            #6
            Originally posted by nuno
            Dang, what happened to the Zend Engine 2?
            It was released with 4.3.0-dev, it should be packed with 4.3.0 final IMO.
            It was zapped mainly due to alot of bugs and errors, they then split it into a different tree.

            http://snaps.php.net check out the ones with ZE2, I've had no problems with 4.3.0 on my dev server with vb2 or vb3.
            Scott MacVicar

            My Blog | Twitter

            Comment

            • chrisranjana
              New Member
              • Dec 2002
              • 5

              #7
              php - THE programming language

              East or West PHP is the best !
              Chris, Director, Chrisranjana.com
              Chennai, Tamil Nadu, India.
              Custom php perl mysql web development, freelancing and internet programming.

              Comment

              • Jet
                Senior Member
                • Oct 2001
                • 186

                #8
                Is there any known issue with vBulletin 2.2.x running PHP 4.3 ?

                When 4.2.x was released, I can remember some minor upgrade to VB to work with (first of all, for instance, the fields name in each select).

                Thank you.

                Comment

                • Cyborg from DH
                  Senior Member
                  • Nov 2002
                  • 305

                  #9
                  As far as I've seen there are no issues with vB2.2.8 and PHP 4.3.0.

                  They've worked flawlessly.

                  Comment

                  • ccd1
                    Senior Member
                    • Jun 2002
                    • 1494

                    #10
                    I'm running PHP 4.3.0 and so far, no errors to report.

                    Comment

                    • Fusion
                      Senior Member
                      • Aug 2001
                      • 4346
                      • 3.8.x

                      #11
                      Originally posted by baragon0
                      I'm running PHP 4.3.0 and so far, no errors to report.
                      Well, I'm sorry to spoil the party, but if you good people could have a look at http://www.vbulletin.com/forum/showt...threadid=61856, you'll see that I may have found some issues with 4.3.0.

                      I'd appreciate some help.
                      Toddler from Hell

                      Comment

                      • Bosco
                        Member
                        • Feb 2002
                        • 42
                        • 3.7.x

                        #12
                        Originally posted by Fusion
                        Well, I'm sorry to spoil the party, but if you good people could have a look at http://www.vbulletin.com/forum/showt...threadid=61856, you'll see that I may have found some issues with 4.3.0.

                        I'd appreciate some help.
                        What about the mstring problem with characters like time missing on posts with VB? Is that resolved if mstring is enabled?

                        Comment

                        • NTLDR
                          Senior Member
                          • Apr 2002
                          • 212
                          • 3.0.0 Gamma

                          #13
                          Originally posted by Bosco
                          What about the mstring problem with characters like time missing on posts with VB? Is that resolved if mstring is enabled?
                          I complied 4.3 using --with-mbstring and haven't had any problems with it at all.
                          vBulletin.org Moderator
                          The Sisters Three Charmed Discussion Forums

                          Comment

                          widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                          Working...