fidzu : PHP

This week, Symfony 6.4.38, 7.4.10, and 8.0.10 maintenance versions were released. In addition, we published the first beta of Symfony 8.1 so you can test it before its final release in three weeks. Meanwhile, we shared more information about the SymfonyDay…

10 May 2026 7:06am GMT

Join us on June 4, 2026, in Montreal at L'Espace Quartier Latin (UQAM) for a unique SymfonyDay. Eight expert speakers are ready to share their knowledge with the community! 🎤 Speaker announcement! Discover "CQRS in Symfony: yes, but calm down" presented…

08 May 2026 1:00pm GMT

Contributed by Robin Chalas in #62917…

08 May 2026 7:19am GMT

SymfonyDay Montreal 2026 schedule is live! Join us on June 4, 2026, at L'Espace Quartier Latin (UQAM) for a day of pure PHP and Symfony expertise. 🎤 Speaker announcement! Florian Merle, Backend Developer, baksla.sh, will present "Empower creativity…

07 May 2026 1:00pm GMT

Contributed by Nicolas Grekas in #63612 ,…

07 May 2026 7:38am GMT

Symfony 8.1.0-BETA1 has just been released. This is a pre-release version of Symfony 8.1. If you want to test it in your own applications before its final release, run the following commands: 1 2 3 $ composer config minimum-stability…

06 May 2026 2:29pm GMT

Symfony 6.4.38 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip…

06 May 2026 1:07pm GMT

Symfony 8.0.10 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip…

06 May 2026 12:42pm GMT

Symfony 7.4.10 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip…

06 May 2026 12:17pm GMT

Contributed by Yonel Ceruto in #62567…

06 May 2026 6:47am GMT

Last week I helped the folks at ezSystems debug some APC problems they were having. The problems ended up being a 64bit architecture problem (they have uber-fast Opterons) and the bug is now fixed in 2.0.3.

Today I received Python & XML from them (off my Amazon wishlist). Thanks guys!

On a side note, my wishlist seems borked. The list I get when I search on my email address or name is not the same one I can edit when I log into the site.

01 Apr 2004 6:53pm GMT

1st of April 2004 get's to it's end and I guess it's time, to summarize the recent April fools a bit. Not that I think anyone in the world believes in them, but some were quite funny:

1. Changes to case sensitivity in PHP.
Alan Knowles announced that PHP will change to the studlyCase API and therefor will get everything broken by changing established functions.

2. IBM takes over Zend.
Myself hacked a little article about IBM taking over Zend to make PHP a compete of Java.

3. The first PHP virus has been seen.
Wasn't there one last year, too?

4. PHP has been overtaken by Micro$oft.
Mhhh... a little bit unreliable, if they had been taken over by IBM this morning... Maybe one should first look, what others wrote...

5. And finally, PHP4 and 5 showed their real faces...
Take a look at a phpinfo() output!

I guess I missed some, so feel free to comment on this entry, if you found another!

01 Apr 2004 5:49pm GMT

Symantec have a report of the virus here. I've yet to see any of the PHP news sites picking up on it but, using a virtual host account, managed to deliberately expose some PHP scripts to it. From examining the infected scripts, what's disturbing is once infected, every tim...

01 Apr 2004 12:19pm GMT

Michael Harrison, an English poet, was once asked how to become a good writer. He replied, "If you want to be a good writer, write. You don't wait for inspiration."

Don Box, co-author of SOAP, gives similar advice:

• Read fewer specifications,
• write more applications,
• write less code by using tools that generate code automatically,
• and remember that humans matter, so if you must write a specification, make it legible.

01 Apr 2004 8:00am GMT

As IBM and Zend announced in the early morning hours, both signed a buyout contract yesterday. Irving Wladawsky-Berger (IBM vicepresident of technology and strategy): "We are now taking the consequences of Sun's behavior to leave Java closed source. The power of open source has been proven by years now if Sun is to narrow-minded to see the importance of open source, we have to select another partner.".

IBM stated, that PHP5 will become the main plattform for at first all web and network related producst. For that, PHP will be integrated into IBM Websphere until August 2003. Zeev Suraski from Zend: "IBM is an important strategic partner for us. Now we are able to compete with Java and .NET.". Irving Wladawsky-Berger sees even much more potential for PHP in IBM. For that, it will be integrated into the Lotus Domino/Notes series and will replace the proprietary script language used, whith Lotus Notes 7.0.

Shortly after this announcement, the PHP community announced some seriouse decisions on recently discussed problems. PHP will now replace all under_score_function names with studlyCaps writing. Andi Gutmans: "All major languages use studly caps for their naming convention, so PHP has to fit in this schema." The community itself introduced some more changes.

See Alan Knowles for more info
and the announcement of IBM and Zend here.

01 Apr 2004 6:55am GMT

Big thanks to Rasmus for pointing out why my presumably non-pic libphp4.so was actually pic. Apparently, it's not enough to not pass -prefer-pic to libtool, you need to actually pass -prefer-non-pic. With this I get identical shared performance to the static compile. The stats results have been amended to reflect this. The downside of building your shared libraries without -fpic is that they end up not sharing a memory footprint, but you get the management benefit of being able to recompile specific extensions (or PHP itself) without recompiling Apache, which is nice.

01 Apr 2004 3:58am GMT

After rather heated discussions on IRC over the last week, concerning StudlyCaps naming and php core. The core php developers (from what I saw) appear to be close to agreeing on some changes for PHP5.1

• Finally we will get Case sensitive functions / methods
  
• the _ underscore naming convention for PHP functions will be gradually replaced with StudlyCaps for all objects, methods and functions.

Alot of the discussion centered around the impact this may have on old code, In general it was the concensus that it would only break really bad code hosted on sourceforge, which wouldnt be a complete disaster..

I have to admit it was pretty rare to see such agreement in such an argumentative group, but they considered consitency to be the ultimate goal, and it would make the life fo developers considerably easier.

Some of the core deadlines in the strategy are

• Changing the manual to add the extra 500+ functions, and make the old ones redirect to new ones, (eg. going to www.php.net/array_count would redirect automatically to www.php.net/arrayCount) this is expected to be complete by July
  
• For adding the aliases in, Lukas Smith was unanomously nominated to undertake the code changes, normally a core PEAR developer this will be his first major expedition into the C source code. it is expected that this will be completed by November.
  

In the meantime, they do recommend that if you are using any of the existing under_scored methods, that you write short wrappers to ensure that when they are removed in PHP5.1, that your applications work:
eg.

if (!function_exists('array_count')) {
    function array_count($a) { return arrayCount($a); }
}

View Extended Entry

01 Apr 2004 1:59am GMT

Was perturbed to read one on the comments on Zend's PHP5 - Ask the Experts; Q: In PHP 5 (rc1-dev)... is there any reason why you can't do this? if (!defined('SOMETHING')) { class HelloWorld { .... } } A: This is a problem we know abou...

31 Mar 2004 6:58pm GMT

It's important to admit when you're wrong, and my final judgment as to the performance it of running PHP as a DSO inside Apache here was wrong.

Following Ilia's good advice, I just decided to get to the meat of the matter by benchmarking PHP scripts. Interestingly, the more complex the script, the higher the overhead. On a simple 'hello world' type page, ab showed around a 4 performance difference, close to what I would expect. On a more complex page though (the Smarty demo page) I consistently got a 30 performance difference.

In retrospect I think the flaw with my original tests is that the functions called from within PHP are almost exclusively PIC code as well, so you actually incur a larger overhead the more frequently you call them.

For those interested, raw ab results are up here.

31 Mar 2004 6:32pm GMT

Planet PHP recently got a link on PEARweb.

31 Mar 2004 6:04pm GMT