jakubmisek on master
core: avoids string alloc in ty… mysqli: fixes missing get_resul… (compare)
class X {
function __construct(int ...$args) {
//print_r( $args );
}
}
PEAR_Error
?
__destruct
is not called deterministically. I think the destruct is called after laravel resets itself for the next test and then fails because its not in the state the original test expected, I'll keep looking into this to see if this is actually the case though (I can't really reproduce this easily, I'll probably disable the __destruct
for now)
The following psuedo-code is what happens as far as I can tell:
SetupLaravelApplication();
{ // create new scope
$obj = new Command();
}
DestroyLaravelApplication();
In PHP $obj is destroyed at the end of the scope, in C# its destroyed whenever (and from another thread (the finalizer thread)?) so that causes some problems