Display TypeExceptions like normal exceptions

We currently don't show the argument at which the error actually
occured in the trace - should probably either add it or don't
display a

Display TypeExceptions like normal exceptions

We currently don't show the argument at which the error actually
occured in the trace - should probably either add it or don't
display args on incomplete frames altogether, otherwise this'll
probably be confusing.

show more ...

Make zend_get_exception_base static.

Soap extension can use other API functions.

Tweak uncaught exception message display

This implements a reduced variant of #1226 with just the following
change:

-Fatal error: Uncaught exception 'EngineException' with messa

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.

show more ...

Fix handler double copy.

Remodel exceptions based on Throwable interface

Added Throwable interface that exceptions must
implement in order to be thrown. BaseException
was removed, EngineException renamed to

Remodel exceptions based on Throwable interface

Added Throwable interface that exceptions must
implement in order to be thrown. BaseException
was removed, EngineException renamed to
Error, and TypeException and ParseException
renamed to TypeError and ParseError. Exception
and Error no longer extend a common base
class, rather they both implement the Throwable
interface.

show more ...

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.

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.

show more ...

Fix exception leak in interactive console

Shows up there because it throws at E_WARNING severity level and
as such leak detection is not suppressed.

Minor Typo in Comment

Fixed res leak

Fixed res leak

codes standard

More fixes for bug #69152

Convert fatal errors into EngineException

Use zend_error_noreturn() for fatal errors

Fixed error messages

Refactor error messages to only append defined in the event of rendering as a fatal error. Fix relative typehints to not work

Refactor error implementation significantly to centralize error mode behavior. Add zend_internal_type_error() function

Implement engine exceptions

RFC: https://wiki.php.net/rfc/engine_exceptions_for_php7

Pending changes regarding naming of BaseException and whether it
should be an interface.

zend_read_property() has to provide a holder for return value.
Previously it was possible that zend_read_property() returned pointer to zval allocated on stack.

bump year

bump year

Bump year

trailing whitespace removal

first shot remove TSRMLS_* things

Fixed compilation warnings