I’m already busy preparing for the international PHP conference, in Munchen, Germany. I’m giving two talks : on about PHP 5.6 and the second about static audits. Besides, being an impressive conference, I’ll be happy to visit one of my first conferences ever.
With versions stretching from PHP 5.3 to PHP 5.6, PHP has several major published versions, that require special attention when migrating. Beyond checking for compilation, the code must be reviewed to avoid pitfalls like obsoletes functions, new features, change in default parameters or behavior. We’ll set up a checklist of such traps, and ways to find them in the code and be reading for PHP 5.6.
Even nowadays, PHP code is mostly manually audited. Expert pore over actual code, in search for bugs or code smells. Actually, it is possible to have PHP do this work itself ! Strengthened with the internal Tokenizer, bolstered by the manual, it is able to scan thousands of lines of code, without getting bored, and bringing pragmatic pieces of wisdom: official manual recommendations, version migration, code pruning and security. In the end, it deliver a global overview of the code, without reading it.