Adding ignoreStrictCheck option for call_user_func_array, if throwing exception
added tests for exceptions thrown in __call()
[ext] Mirroring PHP change for call_user_func_array, see #1286
feature #1286 Adding ignoreStrictCheck option for call_user_func_array, if throwing exception (fabpot)

This PR was merged into the master branch.

Discussion
----------

Adding ignoreStrictCheck option for call_user_func_array, if throwing exception

Same as #1236 with added unit tests and C extension support (to come).

"I experienced the issue when using FuelPHP's ORM with EAV containers. When I tried to reference a property that was not defined I expected to get null, but instead the whole application stopped because an exception was thrown in the ORM, that no such function is present.

I couldn't find other possible exception that could be thrown when this function is called, so I assumed it's safe to take the ignoreStrictCheck into consideration here."

Commits
-------

1abf5d9 [ext] Mirroring PHP change for call_user_func_array, see #1286
9ab290b added tests for exceptions thrown in __call()
c711d37 Adding ignoreStrictCheck option for call_user_func_array, if throwing exception
fixed markup
prepared the 1.15.0 release
bumped version to 1.15.1-DEV
added an error message when trying to import an undefined block from a trait
bug #1288 added an error message when trying to import an undefined block from a trait (fabpot)

This PR was merged into the master branch.

Discussion
----------

added an error message when trying to import an undefined block from a trait

Commits
-------

a2c6db7 added an error message when trying to import an undefined block from a trait
Fixed rendering of ``-3``

The missing space between "``-3``" and "(this is just syntactic[...])" led to the ``-3`` being rendered wrong. The parser must've ignored the closing "``" when it was directly followed by a non-space character.
minor #1291 Fixed rendering of ``-3`` (ureimers)

This PR was merged into the master branch.

Discussion
----------

Fixed rendering of ``-3``

The missing space between "``-3``" and "(this is just syntactic[...])" led to the ``-3`` being rendered wrong. The parser must've ignored the closing "``" when it was directly followed by a non-space character.

Commits
-------

d8ea1b1 Fixed rendering of ``-3``