Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.
http://wiki.php.net/rfc/e-user-deprecated-warning
cu, Lars
Lars Strojny wrote:
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.http://wiki.php.net/rfc/e-user-deprecated-warning
cu, Lars
+1 I loves me some trigger_error() and I like to deprecate things.
Right now I generate an E_USER_WARNING which is not very accurate.
--
Brian Moon
Senior Web Engineer
When you care enough to spend the very least.
http://dealnews.com/
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.
+1
Thanks for your work :-)
--
Pierre
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.
+1
Sorry, I thought I'd already given my vote right after reading the
Wiki entry.
--
</Daniel P. Brown>
Better prices on dedicated servers:
Intel 2.4GHz/60GB/512MB/2TB $49.99/mo.
Intel 3.06GHz/80GB/1GB/2TB $59.99/mo.
Dedicated servers, VPS, and hosting from $2.50/mo.
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.
i definitely like the E_USER_DEPRECATED :D im curious though, about
E_DEPRECATED. is this for deprecated functions at the C level, or just the
php api? the reason i ask is because deprecation notices are already issued
via the E_STRICT level, for example, when using is_a() today, w/ E_STRICT
enabled, the following is generated
Strict standards: is_a(): Deprecated. Please use the instanceof operator in
...
would, perhaps, the deprecation level for is_a() move to E_DEPRECATED (i
noticed its still there in 5.3)?
-nathan
+1 from me
in PHP 5.3 deprecation notices have been split of from E_STRICT into
E_DEPRECATED
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.i definitely like the
E_USER_DEPRECATED:D im curious though, about
E_DEPRECATED. is this for deprecated functions at the C level, or just the
php api? the reason i ask is because deprecation notices are already issued
via theE_STRICTlevel, for example, when usingis_a()today, w/E_STRICT
enabled, the following is generatedStrict standards:
is_a(): Deprecated. Please use the instanceof operator in
...would, perhaps, the deprecation level for
is_a()move toE_DEPRECATED(i
noticed its still there in 5.3)?-nathan
On Sat, Jul 19, 2008 at 4:55 AM, Lars Strojny lstrojny@php.net
wrote:Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the
new
error level.i definitely like the
E_USER_DEPRECATED:D im curious though, about
E_DEPRECATED. is this for deprecated functions at the C level, or
just the
php api? the reason i ask is because deprecation notices are
already issued
via theE_STRICTlevel, for example, when usingis_a()today, w/
E_STRICT
enabled, the following is generatedStrict standards:
is_a(): Deprecated. Please use the instanceof
operator in
...would, perhaps, the deprecation level for
is_a()move to
E_DEPRECATED(i
noticed its still there in 5.3)?
deprecation of is_a() was a mistake that has been reverted.
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
On Sun, Jul 20, 2008 at 2:02 PM, Lukas Kahwe Smith mls@pooteeweet.org
wrote:
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.i definitely like the
E_USER_DEPRECATED:D im curious though, about
E_DEPRECATED. is this for deprecated functions at the C level, or just
the
php api? the reason i ask is because deprecation notices are already
issued
via theE_STRICTlevel, for example, when usingis_a()today, w/E_STRICT
enabled, the following is generatedStrict standards:
is_a(): Deprecated. Please use the instanceof operator
in
...would, perhaps, the deprecation level for
is_a()move toE_DEPRECATED(i
noticed its still there in 5.3)?deprecation of
is_a()was a mistake that has been reverted.
thats interesting, may i ask when that would be a better choice that
instanceof ?
and anyway, there are other examples as well, for example mktime(),
PHP Strict standards: mktime(): You should be using the time() function
instead in ...
would this be another candidate to port to E_DEPRECATED ? so i imagine
there will be some work to convert those E_STRICT errors regarding
deprecation to the new E_DEPRECATED level. maybe that should go along w/
the patch. as a matter of consistency, i think it would be best to move all
E_STRICT errors regarding deprecation to E_DEPRECATED in a single patch,
rather than a piecemeal fashion.
-nathan
and anyway, there are other examples as well, for example
mktime(),PHP Strict standards:
mktime(): You should be using thetime()
function
instead in ...would this be another candidate to port to
E_DEPRECATED? so i
imagine
there will be some work to convert thoseE_STRICTerrors regarding
deprecation to the newE_DEPRECATEDlevel. maybe that should go
along w/
the patch. as a matter of consistency, i think it would be best to
move all
E_STRICTerrors regarding deprecation toE_DEPRECATEDin a single
patch,
rather than a piecemeal fashion.
someone already took care of this job. i presume its pretty complete,
since all cases should be easily greppable. try out 5.3 and lets us
know if you find any places that still need to be migrated.
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
Hi everbody,
regarding my mail from yesterday, I've also created an RFC for the new
error level.http://wiki.php.net/rfc/e-user-deprecated-warning
cu, Lars
A large +1 from me too.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."