php-src/Zend/tests/bug48215_2.phpt

--TEST--
Bug #48215 - parent::method() calls __construct, case sensitive test
--FILE--
<?php
class a {
	public function __CONSTRUCT() { echo __METHOD__ . "\n"; }
	public function a() { echo __METHOD__ . "\n"; }
}
class b extends a {}
class c extends b { 
	function __construct() {
		b::b();
	}
}
$c = new c();
?>
===DONE===
--EXPECTF--
Fatal error: Uncaught EngineException: Call to undefined method b::b() in %s:%d
Stack trace:
#0 %s(%d): c->__construct()
#1 {main}
  thrown in %s on line %d
Make the check case sensitive, and since we can only have a constructor that matches the class name or is __construct its probably safe to just check for __. This means we can skip lowering the function_name, which is hard to be binary safe sine we don't store the length. If we just did a zend_hash_exists lookup we'd be fine since its stored lowercased already :) 2009-06-19 11:29:47 +08:00			`--TEST--`
			`Bug #48215 - parent::method() calls __construct, case sensitive test`
			`--FILE--`
			`<?php`
			`class a {`
			`public function __CONSTRUCT() { echo __METHOD__ . "\n"; }`
			`public function a() { echo __METHOD__ . "\n"; }`
			`}`
			`class b extends a {}`
			`class c extends b {`
Finish PHP 4 constructor deprecation 2015-03-31 22:10:06 +08:00			`function __construct() {`
Make the check case sensitive, and since we can only have a constructor that matches the class name or is __construct its probably safe to just check for __. This means we can skip lowering the function_name, which is hard to be binary safe sine we don't store the length. If we just did a zend_hash_exists lookup we'd be fine since its stored lowercased already :) 2009-06-19 11:29:47 +08:00			`b::b();`
			`}`
			`}`
			`$c = new c();`
			`?>`
			`===DONE===`
			`--EXPECTF--`
Tweak uncaught exception message display This implements a reduced variant of #1226 with just the following change: -Fatal error: Uncaught exception 'EngineException' with message 'Call to private method foo::bar() from context ''' in %s:%d +Fatal error: Uncaught EngineException: Call to private method foo::bar() from context '' in %s:%d The '' wrapper around messages is very weird if the exception message itself contains ''. Futhermore having the message wrapped in '' doesn't work for the "and defined" suffix of TypeExceptions. 2015-05-18 00:35:18 +08:00			`Fatal error: Uncaught EngineException: Call to undefined method b::b() in %s:%d`
Display EngineExceptions like ordinary exceptions TypeException stays as-is for now because it uses messages that are incompatible with the way exception messages are displayed. closure_038.phpt and a few others now show that we're generating too many exceptions for compound operations on undefined properties -- this needs to be fixed in a followup. 2015-05-16 03:04:07 +08:00			`Stack trace:`
			`#0 %s(%d): c->__construct()`
			`#1 {main}`
			`thrown in %s on line %d`