Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61912
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.184 cause and error)
Message-ID: <5018EA9E.1010603@lsces.co.uk>
Date: Wed, 01 Aug 2012 09:36:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <50163FAD.4020004@lsces.co.uk> <5016A5A8.50506@lerdorf.com> <5018CA7E.5070802@lsces.co.uk> <5018CC83.4030002@sugarcrm.com> <5018D2D1.2040004@lsces.co.uk> <5018D80D.7020502@sugarcrm.com> <5018DDD4.7010608@lsces.co.uk> <5018E16C.8020703@sugarcrm.com> <5018E419.7040504@lerdorf.com>
In-Reply-To: <5018E419.7040504@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Bringing users along ...
From: lester@lsces.co.uk (Lester Caine)

Rasmus Lerdorf wrote:
>>> Only with short tags on ... 5.4 has detached it from that, but 5.3 still
>>> >>switches it off by default, and convincing ISP to switch short tags on again is
>>> >>a lost cause:(  Fixing it in PHP5.3 was rejected:(
>> >
>> >Errm... So you are complaining we're not going back in time now and make
>> >different decision about PHP 5.3 that was made years ago? Or what is
>> >your point exactly?
> Note also that we have been*extremely*  conservative with the
> short_open_tag setting because we know it can break old code. To this
> day even in PHP 5.4 it is still on by default as it was in PHP 5.3.
> Since PHP 5.1.0 which was released in 2005 we have suggested that people
> disable it in their php.ini because of the obvious problems it causes
> with respect to other things that use the XML PI tag, but we have in no
> way forced their hands. If you simply upgraded PHP and didn't change
> your php.ini, nothing related to short_open_tags would have broken in
> the past 15 years.

Then can you explain why <?= has stopped working on shared hosting on a number 
of ISP's who have recently updated from 5.2 to 5.3 ...
The default on PHP5.3 is to switch 'short_open_tag' off? which also disables <?= 
which is a bit of a problem when the sites are using templating which relies on 
it :( The horse has bolted now, but it would have been nice when this particular 
problem was highlighted that PHP5.3 was backported with the fix that HAS been 
applied to 5.4 ...
This is an example of a simple problem, not of 'buggy code' :(

-- 
Lester Caine - G8HFL
-----------------------------
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