jakubmisek on master
emit: numeric conversions betwe… (compare)
jakubmisek on master
System.Decimal -> PhpValue (compare)
jakubmisek on master
comparison operators reviewed, … (compare)
jakubmisek on master
comparison error messages clean… (compare)
jakubmisek on master
PhpNumber.Default (compare)
jakubmisek on master
fix type of unpack function (compare)
@calvinbaart we've changed the getLastError()
implementation so it never returns FALSE
. Note in PHP it does return FALSE
sometimes but it is not documented and I think developers (and frameworks) do not expect it anyway.
The only scenario where it can be used would be if someone would like to check if any of date-parsing function were used already by checking getLastError()
is FALSE
.
eval()
think is not ready for it yet. Note compiler needs the whole context, all the classes and dependencies. It cannot just compile a piece of it, or at least not efficiently.
0.9.9
to 1.0.0
(-dev
)!
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)