+1

There's a reason that web browser APIs have so much cruft (user-agent
string, yuck), and there's a reason for ECMAScript 5's "use strict" instead
of "use legacy". Old code should work without changing it. Otherwise a lot
of things break which take a lot of time to fix, and even worse, devs can
forget about some project (I know I have), and it breaks without warning.
On Jul 19, 2012 1:40 PM, "Lester Caine" <les...@lsces.co.uk> wrote:

> Daniel Macedo wrote:
>
>> What I was stating is that: IF you want to keep the old way of doing
>> things around instead of removing them, it should be "change
>> settings/tag/whatever so it work as the old way" and not "change it so
>> it works the new way", that was my only point.
>>
>
> Obviously you don't support a lot of active websites?
> 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.
> I WILL have all these sites moved to machines I can control all the
> configurations of but it all takes time. We simply do not have the time to
> rewrite everything every time someone decides they don't like 'the old
> way', but we need the security fixes since every exploit is better
> advertised than the new features !!!
>
> 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.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - 
> http://lsces.co.uk/wiki/?page=**contact<http://lsces.co.uk/wiki/?page=contact>
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - 
> http://rainbowdigitalmedia.co.**uk<http://rainbowdigitalmedia.co.uk>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Reply via email to