Andrew Faulds wrote:
Hmm, in that case, why do ini defaults differ significantly from those compiled
in?
There was a discussion about that not long ago? Aren't the PHP5.4 bits now all
tidied so that the defaults match a production .ini file? So only development
changes something?
I've not ch
Hmm, in that case, why do ini defaults differ significantly from those compiled
in?
--
Sent from Samsung Mobile
Andrew Faulds
http://ajf.me/
Johannes Schlüter wrote:
On Wed, 2012-08-01 at 13:38 +0100, Lester Caine wrote:
> The default if it's not included in the .ini is ON, but the
> sample .i
On Aug 1, 2012, at 7:01 AM, Johannes Schlüter wrote:
> On Wed, 2012-08-01 at 13:38 +0100, Lester Caine wrote:
>> The default if it's not included in the .ini is ON, but the
>> sample .ini's both switch it off, and that is what the distributions
>> follow when creating a clean install.
>>
>> ALL
On 08/01/2012 05:38 AM, Lester Caine wrote:
> Andrew Faulds wrote:
>>> Then can you explain why >> a number
>>> >of ISP's who have recently updated from 5.2 to 5.3 ...
>> Which? "A number of ISP's"? How many are we talking about?
>> Also, is it our problem if ISPs changed their configuration during
On Wed, 2012-08-01 at 13:38 +0100, Lester Caine wrote:
> The default if it's not included in the .ini is ON, but the
> sample .ini's both switch it off, and that is what the distributions
> follow when creating a clean install.
>
> ALL that was required when the problem was identified was that ha
Andrew Faulds wrote:
Then can you explain why of ISP's who have recently updated from 5.2 to 5.3 ...
Which? "A number of ISP's"? How many are we talking about?
Also, is it our problem if ISPs changed their configuration during an upgrade?
How do we know it's our fault? Debian or RedHat or some o
Hi!
On 01 August 2012 at 09:36 Lester Caine wrote:
> 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
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 no
On 08/01/2012 12:57 AM, Stas Malyshev wrote:
> Hi!
>
>> 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 c
Hi!
> 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
diff
Stas Malyshev wrote:
setting without considering the consequences (
Err, I'm not sure what you mean - 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 wa
On Tue, Jul 31, 2012 at 11:55 PM, Lester Caine wrote:
> Stas Malyshev wrote:
>
>> Helping to solve the problem would also help everybody else upgrade TO
>>> PHP5.4?
>>>
>> OK, so what help do you require?
>>
> PEAR and PECL that work with PHP5.4 out of the box?
> At least the core of PEAR that do
Hi!
> PEAR and PECL that work with PHP5.4 out of the box?
> At least the core of PEAR that does not throw strict warnings from a stock
> install of PHP5.4 as E_STRICT is on.
For PEAR is think it is a wrong list, as for PECL most extensions are
maintained by their maintainers, and internals speci
Stas Malyshev wrote:
Helping to solve the problem would also help everybody else upgrade TO PHP5.4?
OK, so what help do you require?
PEAR and PECL that work with PHP5.4 out of the box?
At least the core of PEAR that does not throw strict warnings from a stock
install of PHP5.4 as E_STRICT is o
Hi!
> The current raft of PHP problems arise from the fact that "we actually put a
> lot
> of emphasis on not breaking backward compatibility" seems just to be lip
> service
> to the real problem ... Taking stuff out in PHP5.4 would be fine if people
> are
So what would happen if it would b
Rasmus Lerdorf wrote:
Having just been helping another unsophisticated user, the growing
>problem of incompatibility between versions is starting to hit harder.
>So can developers please start taking a little more care with the
>support of existing users!
Lester, we get it. Your job is to mainta
On 07/30/2012 01:02 AM, Lester Caine wrote:
> Having just been helping another unsophisticated user, the growing
> problem of incompatibility between versions is starting to hit harder.
> So can developers please start taking a little more care with the
> support of existing users!
Lester, we get
Adam Harvey wrote:
What, specifically, have you found that isn't covered in the release
notes and/or migration guide for PHP 5.3 and 5.4? Documentation bugs
would be awesome here. (Patches would be even more awesome.)
It's hard to improve this without detailed information, since the
migration gu
On 30 July 2012 16:02, Lester Caine wrote:
> Moving people from 5.2 is probably going to be as bad as killing off PHP4
> and 4.6% of sites are still using that! But the main problem starting to
> happen now is that developers are upgrading projects to use 5.3 and 5.4
> features, but simply assumin
19 matches
Mail list logo
