From c9f27ee4227268bc74fc54e0e06102317e614804 Mon Sep 17 00:00:00 2001 From: Nikita Popov Date: Fri, 15 May 2015 21:04:07 +0200 Subject: 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. --- ext/intl/tests/breakiter___construct.phpt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'ext/intl/tests/breakiter___construct.phpt') diff --git a/ext/intl/tests/breakiter___construct.phpt b/ext/intl/tests/breakiter___construct.phpt index a818075a30..a1e59ddf5d 100644 --- a/ext/intl/tests/breakiter___construct.phpt +++ b/ext/intl/tests/breakiter___construct.phpt @@ -11,4 +11,7 @@ ini_set("intl.error_level", E_WARNING); new IntlBreakIterator(); --EXPECTF-- -Fatal error: Call to private IntlBreakIterator::__construct() from invalid context in %s on line %d +Fatal error: Uncaught exception 'EngineException' with message 'Call to private IntlBreakIterator::__construct() from invalid context' in %s:%d +Stack trace: +#0 {main} + thrown in %s on line %d -- cgit v1.2.1