php core

In a new post to his blog Ilia Alshanetsky takes a look at PHP's output buffering feature and some interesting things he found when testing some recent code (hint: it has to do with PHP's "interesting" management of the buffer).

Elizabeth Naramore, host of the "Future of PHP" webcast series for EngineYard has put out a call for PHP internals developers inviting ones that would like to chat a bit.

Consider this a call to the PHP Internals team. We've been doing a series of panel discussions over at Engine Yard about PHP-related frameworks and where they are going in the future, but one important piece that's missing is the discussion about the future of the PHP core.

Article originally from rooJSolutions blog
Well, for the first time in a very long while I had to post to the PHP core developers list last week, unfortunately the result of which was not particulary usefull.
The key issue was that 5.3.7 accidentally broke is_a() for a reasonably large number of users. Unfortunately the fixup release 5.3.8 did not address this 'mistake', and after a rather fruitless exchange I gave up trying to persuade the group (most peo

In the process of some development he's been doing on various shared modules for PHP, Derick Rethans stumbled across an issue with using Valgrind to test his code:

The Plot to Kill PHP MySQL Extension By Manuel Lemos PHP core developers are planning to kill the PHP original MySQL extension.

If you are using MySQL in your PHP applications for a long time, this may seriously affect you.

Read this article to learn what this means in practice and what you can do about it.

On PHPBuilder.com there's a new tutorial from Octavia Anghel about using the DOM extension to parse XML in a PHP5 application.

The DOM functionality makes it simpler than even the older PHP4 DOM functionality to work with XML messaging and documents.

Howtoforge: "This tutorial shows how to harden PHP5 with Suhosin on a CentOS 5.4 server. From the Suhosin project page: "Suhosin is an advanced protection system for PHP installations that was designed to protect servers and users from known and unknown flaws in PHP applications and the PHP core."

Being the verbose kind, I guess I will put in a summary at the top leaving the original post below for everyone to read all the little details.

Essentially the summary is that I (and many other core developers) agree that HEAD/trunk in its current form was stalling future development on PHP.

Jani indirectly jump started the discussion of moving this stumbling block out of the way by essentially doing two commits that violate the most fundamental rules of PHP development (and common sense courtesy) we have.

A big topic in the world of PHP recently has been interoperability between libraries. With the release of PHP 5.3 and the introduction of namespaces some discussion of new standards around the use of namespaces to promote the interoperability of autoloader implementations has started.