Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Thursday June 25 2015, @12:54PM   Printer-friendly
from the almost-ready dept.

Although the first alpha build of PHP7 was released just two weeks ago, the second build is already being rolled out. A variety of issues from 5.6 have been fixed as part of version 7's alpha build, and a rather comprehensive overview of new features and other language changes have been posted on PHP's official GitHub repository. Some of the most notable improvements are the boasted performance enhancement over PHP5.6, claimed to be up to twice as fast on 64-bit systems, and the well-debated inclusion of scalar type hints.

Additional history of the drafted and implemented changes for version 7 can be seen at the PHP Request for Comments Wiki.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by TheRaven on Friday June 26 2015, @12:14PM

    by TheRaven (270) on Friday June 26 2015, @12:14PM (#201472) Journal
    Choosing UTF-16 as an internal representation is a pretty good indication of completely failing to understand the problem. UTF-32 has the nice characteristic that code points (which are not the same as characters) are always the same size, at the expense of a lot of wasted space. UTF-8 has the nice property that it's a dense encoding, but at the expense of being variable length. UTF-16 is a variable-length encoding that wastes a lot of space. The only reason that you should ever use it is that you're trying to retrofit modern unicode support into APIs that were designed with UCS-2 in mind and so force you to use a 16-bit character type.
    --
    sudo mod me up
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2