php-src/Zend/tests/exception_with_by_ref_message.phpt

--TEST--
Exception with by-ref message
--FILE--
<?php

class MyException extends Exception
{
    public function __construct(&$msg) {
        $this->message =& $msg;
    }
}

$msg = 'Message';
throw new MyException($msg);

?>
--EXPECTF--
Fatal error: Uncaught MyException: Message in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line %d
Drop convert_to usage in zend_exceptions To make everything work correctly with refs. I'm unsure whether the GET_PROPERTY_SILENT distinction is really necessary, because the choice seemed pretty random, but kept it around. 2014-10-07 02:14:30 +08:00			`--TEST--`
			`Exception with by-ref message`
			`--FILE--`
			`<?php`

			`class MyException extends Exception`
			`{`
			`public function __construct(&$msg) {`
			`$this->message =& $msg;`
			`}`
			`}`

			`$msg = 'Message';`
			`throw new MyException($msg);`

			`?>`
			`--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 MyException: Message in %s:%d`
Drop convert_to usage in zend_exceptions To make everything work correctly with refs. I'm unsure whether the GET_PROPERTY_SILENT distinction is really necessary, because the choice seemed pretty random, but kept it around. 2014-10-07 02:14:30 +08:00			`Stack trace:`
			`#0 {main}`
			`thrown in %s on line %d`