PHP7新特性 What will be in PHP 7/PHPNG

來源:互聯網
上載者:User
PHP7將在2015年10月正式發布,我們來看看官網給出的php7 特性
官網: http://www.php7.ca/ https://wiki.php.net/phpng


PHP7新特性( What will be in PHP 7 / PHPNG )
  • Performance Improvements with the addition of PHPNG engine.
  • 使用PHPNG引擎來提升效能


  • JIT - Just in Time compiler
  • 即時編輯器 JIT Compiler_百度百科

  • Abstract Syntax Tree for compilation
  • 抽象文法樹編譯


  • Asynchronous refactoring of the I/O layer.
  • 對I/O層的非同步重構。


  • Multi-threaded build in Web Server
  • 多線程構建Web伺服器


  • Expanded use of ->, [], (), {}, and :: operators
  • 擴充使用 ->, [], (), {}, 和 :: 符號

  • 100% increase in performance
  • 效能提升 100% (應該是QPS)


  • Cool Name: PHPNG
  • 酷名:PHPNG引擎


    為啥直接PHP5.6跳到PHP7(Reasons given why we need to skip to PHP 7)

    There are several reasons of why we shouldn't reuse version 6 for the next major version of PHP.

  • First and foremost, PHP 6 already existed and it was something completely different. The decimal system (or more accurately the infinite supply of numbers we have) makes it easy for us to skip a version, with plenty more left for future versions to come.
  • While it's true that the other PHP 6 never reached General Availability, it was still a very widely published and well-known project conducted by php.net that will share absolutely nothing with the version that is under discussion now. Anybody who knew what PHP 6 is (and there are many) will have a strong misconception in his or her mind as to the contents and features of this new upcoming version (essentially, that it's all about Unicode).
  • PHP 6, the original PHP 6, has been discussed in detail in many PHP conferences. It was taught to users as a done-deal, including detailed explanations about features and behavior (by php.net developers, not 'evil' book authors).
  • PHP 6 was widely known not only within the Internals community, but around the PHP community at large. It was a high profile project that many - if not most - PHP community members knew about.
  • There's lots of PHP 6 information, about the original PHP 6, that exists around the web. Books are the smallest part of the problem.
  • Unlike the 'trivia question' of 'why did we skip into 7?', reusing version 6 is likely to call real confusion in people's minds, with ample information on two completely different versions with entirely different feature sets that have the exact same name.
  • Skipping versions isn't unprecedented or uncommon in both open source projects and commercial products. MariaDB, jumped all the way up to version 10.0 to avoid confusion, Netscape Communicator skipped version 5.0 directly into 6.0, and Symantec skipped version 13. Each and every one of those had different reasons for the skipping, but the common denominator is that skipping versions is hardly a big deal.
  • Version 6 is generally associated with failure in the world of dynamic languages. PHP 6 was a failure; Perl 6 was a failure. It's actually associated with failure also outside the dynamic language world - MySQL 6 also existed but never released. The perception of version 6 as a failure - not as a superstition but as a real world fact (similar to the association of the word 'Vista' with failure) - will reflect badly on this PHP version.
  • The case for 6 is mostly a rebuttal of some of the points above, but without providing a strong case for why we *shouldn't* skip version 6. If we go with PHP 7, the worst case scenario is that we needlessly skipped a version. We'd still have an infinite supply of major versions at our disposal for future use. If, however, we pick 6 instead of 7 - the worst case scenario is widespread confusion in our community and potential negative perception about this version.


  • Supported SAPI

  • cli

  • cgi

  • fpm

  • apache (FastCGI and FPM might be significantly faster if mod_php is built as PIC)

  • apache2handler

  • Supported Extensions

  • bcmath

  • bz2

  • calendar

  • com_dotnet

  • ctype

  • curl

  • date

  • dba

  • dom

  • enchant

  • ereg

  • exif

  • fileinfo

  • filter

  • ftp

  • gd

  • gettext

  • gmp

  • hash

  • iconv

  • imap

  • intl

  • json

  • ldap

  • libxml

  • mbstring

  • mcrypt

  • mysql

  • mysqli

  • mysqlnd

  • odbc (tested with unixODBC and MySQL driver)

  • openssl

  • OPcache

  • pcntl

  • pcre

  • PDO

  • pdo_firebird

  • pdo_mysql

  • PDO_ODBC (tested with unixODBC and MySQL driver)

  • pdo_pgsql

  • pdo_sqlite

  • pgsql

  • Phar

  • posix

  • pspell

  • readline

  • recode

  • Reflection

  • session

  • shmop

  • SimpleXML

  • snmp

  • soap

  • sockets

  • SPL

  • sqlite3

  • standard

  • sysvmsg

  • sysvsem

  • sysvshm

  • tidy

  • tokenizer

  • wddx

  • xml

  • xmlreader

  • xmlwriter

  • xsl

  • zip

  • zlib

  • Unsupported Extensions (not converted yet)

  • interbase

  • mssql

  • oci8

  • pdo_dblib

  • pdo_oci

  • sybase_ct

  • 聯繫我們

    該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

    如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

    A Free Trial That Lets You Build Big!

    Start building with 50+ products and up to 12 months usage for Elastic Compute Service

    • Sales Support

      1 on 1 presale consultation

    • After-Sales Support

      24/7 Technical Support 6 Free Tickets per Quarter Faster Response

    • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.