[wp-trac] [WordPress Trac] #29139: is_a() deprecation/un-deprecation

[WordPress Trac]

#29139: is_a() deprecation/un-deprecation
--------------------------+------------------------------
 Reporter:  area@…        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  3.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Old description:

> https://core.trac.wordpress.org/ticket/23406
>
> ..as a developer, I configure local *AMP to show each message related to
> my project, so to avoid any problem when publishing it at production
> site.
>
> Starting to work with WP I received many warnings (60) related to is_a()
> deprecation. I may solv it placing the statement "error_reporting( 0 );"
> in index.php at root folder but, if I do like that I also blind my
> visibility to other errors.
>
> Due to this back and forth deprecation of is_a() it may be more
> convenient to definitely solve it with its "instanceof" declaration. Is
> there any good reason to leave code with warnings instead of "perfect"
> other than the priority to more complex issues? Security, of course, has
> to be the first but, if you need more resources at this stage I may do
> the change the 60 occurrences of is_a(), check it and send it to you.
>
> Best wishes,
>
> Carmine Iaciofano
> Area

New description:

 #23406

 ..as a developer, I configure local *AMP to show each message related to
 my project, so to avoid any problem when publishing it at production site.

 Starting to work with WP I received many warnings (60) related to is_a()
 deprecation. I may solv it placing the statement "error_reporting( 0 );"
 in index.php at root folder but, if I do like that I also blind my
 visibility to other errors.

 Due to this back and forth deprecation of is_a() it may be more convenient
 to definitely solve it with its "instanceof" declaration. Is there any
 good reason to leave code with warnings instead of "perfect" other than
 the priority to more complex issues? Security, of course, has to be the
 first but, if you need more resources at this stage I may do the change
 the 60 occurrences of is_a(), check it and send it to you.

 Best wishes,

 Carmine Iaciofano
 Area

--

Comment (by SergeyBiryukov):

 Related: #10264, #14131, #19381, #23406, #25672.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29139#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform