On Thu, Jul 19, 2012 at 1:39 PM, Lester Caine <les...@lsces.co.uk> wrote:

> One little change in PHP5.3.10 or so wiped out a whole block of mine, and
> the fix involved a re-writing all the <?= code across many pages. Simply
> because the ISP would not switch back on short tag.

Did you really go through all code manually to change the short tags?
You should be smarter than that:
https://github.com/danorton/php_replace_short_tags/

> I repeat what I have said many times ... we need a 'long time stable' API
> that just gets security updates so that long time stable sites can be just
> left to work ... If you want to rewrite the manual, then start on a new fork
> of PHP please.

Everyone agrees on a long time stable API, but we also can't be naïve
- since we don't predict the future, yet - and say we'll never change!

One of the reasons major versions are introduced is BC breaks, those
don't come around frequently nor are introduced lightly, and you still
go through the E_DEPRECATED > .ini setting > disabled > optional
extension, for a safe cycle.

I like to think we, as smart developers, would like to see complexity
reduced, even if we need to input a few man-hours into adapting the
old surviving masterpieces.

And with smarter tools like the one mentioned above:
> 3. Build a high-quality tool to convert code automatically to the
> greatest extent possible
With something like that we might even embrace and encourange change
more often, for the platforms we control, instead of living in an ever
more complex compatibility hurt fest that exists on other platforms...

Cheers,
Daniel Macedo

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to