Larry Garfield wrote:
One catch here is that E_STRICT implies no PHP 4 compatibility, as E_STRICT
chokes on PHP 4-style class usage, etc. Drupal 6 had PHP 4 compatibility so
E_STRICT was not an option. The core system was developed to E_ALL standards,
but not all add-on modules (which are the l
On Sunday 25 July 2010 05:55:53 am Reindl Harald wrote:
> A clean designed application has to run the whole time with
> error_reporting = E_ALL | E_STRICT and so you should have seen
> the problems long ago
>
> > This broke Drupal 6 big time and while core has been fixed, contrib is
> > a bit slo
Am 25.07.2010 11:17, schrieb Karoly Negyesi:
> This is a very interesting decision as 5.3.0, compatibility wise, is a
> major release. I always felt it was PHP 6.0 but it was not called so
> because there was a development branched called that (which was later
> abandoned).
This is simply not tr
hi,
On Sun, Jul 25, 2010 at 11:17 AM, Karoly Negyesi wrote:
> Hi,
>
> A mere year after releasing Version 5.3.0 (Version 5.3.0 30-June-2009)
> you are dropping PHP 5.2 support.
We still support 5.2.
There is a huge misunderstanding of "end of active support". It means
that only critical bugs (s
