Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61781
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.132 cause and error)
Message-ID: <50101A51.10602@lsces.co.uk>
Date: Wed, 25 Jul 2012 17:09:53 +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: <CAF+90c_47HtYHnMztUUb7Gd5_gKhpJYJN=G-KJFSmSt_=w2+Lw@mail.gmail.com> <CAKZjf5TbDtSVs7twwVgXH6wCVB0sfQhfasAkCsO47Y_x_9bfuA@mail.gmail.com> <500EDCC7.1020402@ajf.me> <D7DAFE9C-E5F8-4CA1-8807-6E1C5638275A@gmail.com> <CAKZjf5S-GaqhEG2wa86cPo=eV8StkHs9d1TX2SNbXC2x5E1AoQ@mail.gmail.com> <500EE3B9.8010902@ajf.me> <CAKZjf5TdLEzP_hWn0UVLOO4J-BhKeakXdC7d4wmw38ZUMhEyVA@mail.gmail.com> <500EEA76.1030407@ajf.me> <CAL+t6cEJ6D59hZDc38EzsURZPrr1zWecTry2VWCSA_rL=6MknA@mail.gmail.com> <CAKZjf5To5crgc2cL87_sbF3QGuxYihbyKzwxs7QLGkXzWqc7CA@mail.gmail.com> <CAL+t6cF4OK27Wx3RRSgiE1u1zLfn7AzW2SH8PwOg7DN99nezbw@mail.gmail.com> <CAKZjf5Ri2V8_Bydiygm0nN04ACCC2+mWBDaPqLzB2wqkArR2WQ@mail.gmail.com> <CAL+t6cGAyjcVaq3ktpnq7cQHFOmH9kS9OPTgGiah=_ZAuqMDjw@mail.gmail.com> <CAL+t6cFmwdLc_eVAAvpmDY+pQ-y4TmbJw=ci8G8=A7q4EYS7BQ@mail.gmail.com> <501007A4.9000200@ajf.me> <50100C84.3020505@lsces.co.uk> <CAH-PCH6c0wkZSRWzFvBOViWP7o64DN0djPqNT+vPKy_+mo120A@mail.gmail.com>
In-Reply-To: <CAH-PCH6c0wkZSRWzFvBOViWP7o64DN0djPqNT+vPKy_+mo120A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Generators in PHP
From: lester@lsces.co.uk (Lester Caine)

Ferenc Kovacs wrote:
> some/most of the E_STRICT messages are telling you about (possible) problems in
> your code.
The major hurdle here is 'static', and not being able to use a function both 
statically or with $this. PEAR is currently throwing these 'warnings' so is 
there problems in the PEAR code!

> you can decide to ignore them, but imo it is a good thing that we tell those to
> the developer.
The 5.3 stance was 'just switch them off'. With 5.4 changing the rules again, 
the 5.3 stance was no longer tenable so we had to rework all the code which is 
now at the fix PEAR stage! So currently 'E_STATIC' has to be switched off still 
since you can't have all the message being generated.

> the PHP4->PHP5 transition was pretty major, I'm surprised that your "php5 code"
> worked on php4 just fine.
As I have said before and will continue to say. I never USED PHP4, but all of 
the projects I contribute to ran as clean on PHP4 as they did on PHP5.0 and 5.1. 
PHP5.2 introduced the first major break, and was the first time we had to worry 
about a 'transition' ... I don't recognise 4to5 being major as long as you kept 
the PHP5 stuff that was being used tidy. I would have preferred that PHP5.3 had 
simply been called PHP6 and then a PHP5.2 branch maintained for security 
upgrades then I don't think I'd be having nearly as much trouble these days. I 
currently have sites down simply because something is not set right, and I can't 
find the pigging problem. Not just PHP, but also Apache ... Fortunately the 
PHP5.2 systems have not been taken down yet.

-- 
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