Or you as a developer add the following to your code:
error_reporting(error_reporting() & ~E_NOTICE);
at the top of a common file and release a new release and quit f***ing
bing about something which isn't likely to change anytime soon. If
your clients aren't knowledgeable enough to setup th
On Tue, Jul 12, 2005 at 10:33:14PM +0100, Nicholas Telford wrote:
> Firstly, a major version number increment implies a major change (4.2.0
> and 4.3.0 had much more major changes than this iirc). Secondly, as far
> as I'm aware, it doesn't issue a warning, it issues notices which, and
> this h
Korving [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 16, 2005 1:42 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] php 4.4 BC break
>
> I wonder how friendly they will find this notice showing up :) (I know
> most
> of the people out there won't have PHP set
I wonder how friendly they will find this notice showing up :) (I know most
of the people out there won't have PHP set up to show notices, but what
counts for most people, doesn't automatically count for all people)
"Derick Rethans" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On
On Sat, 16 Jul 2005, Ron Korving wrote:
> It doesn't matter how wrong the programmers were by abusing PHP in this way.
> You have to feel sympathy for the fact that these people will be upgrading
> their servers only to find out their code stops working.
It doesn't "stop working", you just get a
> >Lastly, there IS a note in the announcement stating that the major
version
> >increase is due to a non-BC change, I don't see what everyone is
> >complaining about. Perhaps you should request that your users read what
> >they're downloading before they download it.
>
> Wrong, read the announceme
On 7/12/05, Chuck Hagenbuch <[EMAIL PROTECTED]> wrote:
> Yes, they could turn off warnings. But since the code has always run
> cleanly beforehand, they don't think to do that.
It's definitely not the cleanest solution, but for those of you who
want to have a "quick fix" which will hide the proble
At 00:33 13/07/2005, Nicholas Telford wrote:
Firstly, a major version number increment implies a major change (4.2.0
and 4.3.0 had much more major changes than this iirc).
That's the thing, though. 4.4.0 was not pitched as a major release. It
was, and still is, pitched as a bugfix release.
Firstly, a major version number increment implies a major change (4.2.0
and 4.3.0 had much more major changes than this iirc). Secondly, as far
as I'm aware, it doesn't issue a warning, it issues notices which, and
this has been stressed on many occasions, should not be displayed on
production
Quoting Ilia Alshanetsky <[EMAIL PROTECTED]>:
In this case the "facility" was implementing, poorly might I add a
handler for a clearly incorrect behavior. Removing it was not only
appropriate but necessary to encourage proper code being written.
I know that other people have other points of v
On Tue, 12 Jul 2005 13:04:36 -0700
[EMAIL PROTECTED] (Andi Gutmans) wrote:
> Just for the record, most compilers have such "bugs". It happens
> when the compiler is too lenient and allows incorrect code to be
> compiled. I've seen similar things happen in C/C++ and other
> languages.
Sure :) Was
Pierre-Alain Joye wrote:
The bug #33643 is not what I can call "shooting in my own foot".
I'd call that precisely that, I had this happen in my own code a few
times, but looking at the code logically what was being done was clearly
wrong.
There were cases were I fully agree to break BC, bu
Just for the record, most compilers have such "bugs". It happens when the
compiler is too lenient and allows incorrect code to be compiled. I've seen
similar things happen in C/C++ and other languages.
At 09:20 PM 7/12/2005 +0200, Pierre-Alain Joye wrote:
On Tue, 12 Jul 2005 20:53:16 +0200 (CE
On Tue, 12 Jul 2005 20:53:16 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
> On Tue, 12 Jul 2005, Chuck Hagenbuch wrote:
>
> > Relax, I'm not debating the decision. Just:
> >
> > PLEASE can someone put a big fat warning on the php 4.4
> > announcement on www.php.net that it breaks exist
On Tue, 12 Jul 2005, Chuck Hagenbuch wrote:
> Relax, I'm not debating the decision. Just:
>
> PLEASE can someone put a big fat warning on the php 4.4 announcement on
> www.php.net that it breaks existing code?
>
> I already have people upgrading to it and wondering why they get tons of
> warning
Relax, I'm not debating the decision. Just:
PLEASE can someone put a big fat warning on the php 4.4 announcement on
www.php.net that it breaks existing code?
I already have people upgrading to it and wondering why they get tons
of warnings now. We're fixing them as quick as we can, but honest
16 matches
Mail list logo
