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: 3, Interesting) by MichaelDavidCrawford on Thursday June 25 2015, @02:43PM

    by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Thursday June 25 2015, @02:43PM (#200977) Homepage Journal

    A client asked me to figure out why his server kept crashing. Youre running out of swap spave because of memory leaks in your java app. But thats not possible java has garbage collection. That because suns marketing people lied to you.

    I set up a cron to reboot every night.

    Bjarne intended for c++ to solve many problems but for that to happen you have to write c++ the way it is meant to be written.

    mike whats that there in your source. its an initialization list. whats that? it enables transactional commit rollback object initialization.

    100 programmer years in a single executable and they had never even heard of initialization lists.

    Mentor Graphics adopted c++ because object oriented code is reusable. what they got was a clusterfuck. good assembly is reusable but bad c++ is not.

    --
    Yes I Have No Bananas. [gofundme.com]
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by M. Baranczak on Thursday June 25 2015, @07:12PM

    by M. Baranczak (1673) on Thursday June 25 2015, @07:12PM (#201169)

    Youre running out of swap spave because of memory leaks in your java app. But thats not possible java has garbage collection. That because suns marketing people lied to you.

    Did anyone from Sun ever actually claim that memory leaks are "impossible" in Java (as opposed to "much less likely")? Or did you just make that up?

    • (Score: 2) by MichaelDavidCrawford on Thursday June 25 2015, @07:29PM

      by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Thursday June 25 2015, @07:29PM (#201184) Homepage Journal

      I dont know about sun specifically but java fans iften make that claim.

      optimize-it was a java leak detector that borland sold for thousands of dollars per license.

      i dont regard java as being less likely than C++ to leak. it's easy to write leak free c++.

      --
      Yes I Have No Bananas. [gofundme.com]
      • (Score: 2) by fleg on Friday June 26 2015, @02:56AM

        by fleg (128) Subscriber Badge on Friday June 26 2015, @02:56AM (#201363)

        >i dont regard java as being less likely than C++ to leak.

        wow, my bind is moggled.

        >it's easy to write leak free c++

        "easy"? do tell

        • (Score: 2) by MichaelDavidCrawford on Friday June 26 2015, @10:14AM

          not that one cannot write leak free java but that java is harder to get right.

          http://www.warplife.com/tips/code/c++/memory-management/parameters/ [warplife.com]

          --
          Yes I Have No Bananas. [gofundme.com]
          • (Score: 2) by fleg on Sunday June 28 2015, @02:27AM

            by fleg (128) Subscriber Badge on Sunday June 28 2015, @02:27AM (#202305)

            funny. so which bit of that would cover "it's easy to write leak free c++"? operative word being "easy". because "easy" does not mean "this really is a complicated and detailed topic, and I worry that I will scare away beginners." which is from your own intro.

        • (Score: 2) by TheRaven on Friday June 26 2015, @12:08PM

          by TheRaven (270) on Friday June 26 2015, @12:08PM (#201471) Journal
          It actually is much easier to write leak-free C++ with C++14 than it used to be. Basically, never keep bare pointers around and, if you're allocating objects on the heap, always use std::make_unique or std::make_shared. Avoid cyclic data structures (this is probably the hardest. When you have to have cycles, explicitly break them with std::weak_ptr).
          --
          sudo mod me up
          • (Score: 2) by fleg on Sunday June 28 2015, @02:32AM

            by fleg (128) Subscriber Badge on Sunday June 28 2015, @02:32AM (#202308)

            interesting, i havent been keeping up with c++ (all my experience is pre c++11) so i hadnt come across those make_ functions before. thanks.

            • (Score: 2) by TheRaven on Monday June 29 2015, @08:49AM

              by TheRaven (270) on Monday June 29 2015, @08:49AM (#202701) Journal
              If you haven't looked at C++ since before C++11, then I'd suggest taking another detailed look. The language now doesn't completely suck. It's now possible to write quite nice code in C++ (the problems with ABI fragility are still there, sadly). With shared_ptr and unique_ptr, lambdas, the threading and atomics libraries, it has many of the features that you actually want from a modern language. I've gone from hating C++ to tolerating it and using it as my default language for new projects as a result. There's absolutely no way that I'd contribute to a pre-C++11 codebase now though.
              --
              sudo mod me up