Everything

php

RE: Re: E_STRICT

php.internals

Ford, Mike [LSS]

22 years ago

On 19 November 2003 06:12, Andi Gutmans contributed these pearls of wisdom:

> Just a warning.
> I commited your patch. Not sure about the naming but it's the
> status quo for now :)
> Andi
>
>> +                       case E_STRICT:
>> +                               error_type_str = "Strict
>> Standards";
>> +                               break;

As it's a prefix to a more substantive error message, I'd go for something
like "Deprecated Usage" or "No Longer Supported".  (The former would also
match up to an (en|dis)able_deprecated option.)

Cheers!

Mike

--
Mike Ford,  Electronic Information Services Adviser,
Learning Support Services, Learning & Information Services,
JG125, James Graham Building, Leeds Metropolitan University,
Beckett Park, LEEDS,  LS6 3QS,  United Kingdom
Email: m.ford@leedsmet.ac.uk
Tel: +44 113 283 2600 extn 4730      Fax:  +44 113 283 3211

Andi Gutmans

22 years ago

At 11:07 AM 11/19/2003 +0000, Ford, Mike               [LSS] wrote:

>On 19 November 2003 06:12, Andi Gutmans contributed these pearls of wisdom:
>
> > Just a warning.
> > I commited your patch. Not sure about the naming but it's the
> > status quo for now :)
> > Andi
> >
> >> +                       case E_STRICT:
> >> +                               error_type_str = "Strict
> >> Standards";
> >> +                               break;
>
>As it's a prefix to a more substantive error message, I'd go for something
>like "Deprecated Usage" or "No Longer Supported".  (The former would also
>match up to an (en|dis)able_deprecated option.)

Well I'm not sure it will only include deprecated functionality. Maybe
it'll also include some advisory stuff? Like, you better use foo instead of
bar because it's quicker?

Andi