Re: Proposal for serious BC compatibility aka language versioning

> So, if we are talking about PHP 6, then the opening <?php tag should be > accompanied by the version it was written for, it was tested with and then > the engine could switch to a compatibility mode for that version. > > Seems to me that this would solve the problem where a host can't upgrade to > a more modern version for fear of breaking old code. Consequently, open > source packages -- like Drupal I am deeply involved with -- can't use more > modern PHP versions decreasing the "push" for hosts to upgrade. This is a > devilish circle and it'd be great to break it. Agreed with the others that this should not go into the engine (and this should also not really clutter up the Internals list), but if you have a real need for running different versions of PHP for different URLs, you could pretty easily set up multiple FPM backends (one for each version you support) and have Nginx map URLs to these. It would be a maintenance headache, but not the disaster this would be if it had to be maintained in PHP-proper. S