On 2/8/2018 7:38 PM, Mcmuffin Mcguffin wrote:
> What do you think?
>
> Jaroslav Wegner
>
Thanks for the hard work to figure out what the roots of this annoyance
is. This could land in the next PHP version, considering that many other
breaking changes were also allowed in the past, given the foll
2018-02-14 12:40 GMT-03:00 Michael Morris :
> Assert is a statement in PHP 7. Try this code
>
> function foo() {
> debug_print_backtrace();
> return true;
> }
>
> assert(foo());
>
> In PHP 7 only foo() will be in the backtrace. In PHP 5 assert will be
> listed as well.
>
I saw all that `PHP
> In PHP 7 only foo() will be in the backtrace. In PHP 5 assert will be
> listed as well.
>
> What you are proposing has already been done. It's also why
> zend.assertions has three settings: 1: on, -1: off, 0: emulate PHP 5.
> Unless you have code on your hands that is breaking when the -1 setti
My earlier reply was through my phone. I've since read the bug report and
saw your note where you couldn't reproduce it.
Assert is a statement in PHP 7. Try this code
function foo() {
debug_print_backtrace();
return true;
}
assert(foo());
In PHP 7 only foo() will be in the backtrace. In P
The same beharviour, but `assert` as statement also uses 1 character less.
Em 14 de fev de 2018 10:13 AM, "Michael Morris"
escreveu:
On Wed, Feb 14, 2018 at 1:16 AM Pedro Lacerda wrote:
> Hi developers,
>
> Trying to resolve the bug #75950 (that after long hours I found that I
> couldn't rep
On Wed, Feb 14, 2018 at 1:16 AM Pedro Lacerda wrote:
> Hi developers,
>
> Trying to resolve the bug #75950 (that after long hours I found that I
> couldn't reproduce), I observed that if `zend.assertions >= 0` the
> generated code inside `assert()` was indeed executed even if `assert.active
> = o
