|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #50152 ReflectionClass::hasProperty behaves like isset() not property_exists
Submitted: 2009-11-11 18:39 UTC Modified: 2009-11-11 18:53 UTC
From: Assigned: felipe (profile)
Status: Closed Package: Reflection related
PHP Version: 5.3SVN-2009-11-11 (SVN) OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
33 - 7 = ?
Subscribe to this entry?

 [2009-11-11 18:39 UTC]
This change looks to be introduced accidentaly in HEAD, and was MFHd by me times ago. the hasProperty() is currently using the __isset magic method, this doesn't look right from a reflection perspective. It must behaves like property_exists() that doesn't uses the magic stuff.

Reproduce code:

class foo {
	function __isset($a) {
		return 1;

$x = new foo;
$ref = new ReflectionObject($x);

Expected result:

Actual result:
string(1) "b"


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2009-11-11 18:52 UTC]
Automatic comment from SVN on behalf of felipe
Log: - Fixed bug #50152 (ReflectionClass::hasProperty hehaves like isset() not property_exists)
  [5_2 is OK]
 [2009-11-11 18:53 UTC]
This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
Thank you for the report, and for helping us make PHP better.

5.2 is okay, it already checks like property_exists().
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Tue Oct 19 13:03:33 2021 UTC