Hi!
On Thu, 31 Dec 2015, Nikita Popov wrote:
> On Wed, Dec 30, 2015 at 8:55 PM, Derick Rethans wrote:
>
> > While investigating an issue with Xdebug and fast_call/fast_ret, I
> > noticed that the opcodes "associated" with the "finally" statement, are
> > rolled up in the previous line.
> > T
On 30 December 2015 at 23:00, Davey Shafik wrote:
> how will settype($string, int|float), intval(), floatval(), is_numeric()
> and ctype_digit() work with this change?
My understanding is that those functions will continue to work as they
do currently. The numeric literals are resolved by the co
Hey all,
In the PR for adding HTTP/2 Server Push support to curl, Julien raises the
question of adding tests for this feature [1].
This is currently very difficult.
While we have the cli-server, it currently only supports HTTP/1.x. This
means we need another httpd to test against that supports b
On Wed, Dec 30, 2015 at 11:00:55PM +, Davey Shafik wrote:
> You mention no support for numeric strings, but how will settype($string,
> int|float), intval(), floatval(), is_numeric() and ctype_digit() work with
> this change?
>
> I do think if you don't change the semantics for strings to numb
On Wed, Dec 30, 2015 at 8:55 PM, Derick Rethans wrote:
> Hi!
>
> While investigating an issue with Xdebug and fast_call/fast_ret, I
> noticed that the opcodes "associated" with the "finally" statement, are
> rolled up in the previous line.
>
> The code:
>
> 12 function extractFile()
> 3 {
You mention no support for numeric strings, but how will settype($string,
int|float), intval(), floatval(), is_numeric() and ctype_digit() work with
this change?
I do think if you don't change the semantics for strings to number
conversion (which I agree you can't due to BC breaks) there should be
Hey,
some time ago we had a discussion about HashDos protection initiated by Nikita.
There just was one major flaw that it still allowed to crash (fatal error)
background processes with no chance to intercept these.
Hence, an exception is thrown instead in array functions respectively
(parse_s
Hi everyone,
If any of you have looked at http://gcov.php.net any time in the last
three years, you'll probably have noticed an alarming and inexplicably
high number of test failures. And if you've looked at Travis, you'll
have seen much more reasonable numbers (i.e. usually zero).
So, I'd l
Hi!
While investigating an issue with Xdebug and fast_call/fast_ret, I
noticed that the opcodes "associated" with the "finally" statement, are
rolled up in the previous line.
The code:
1
Produces:
line #* E I O op fetch ext return
operands
--
Hi internals!
I'd like to propose for the inclusion of a digit separator in PHP. This will
help to promote the readability of numerical literals in code by enabling for
the underscore character to be used in between digits.
RFC: https://wiki.php.net/rfc/number_format_separator
PR: https://github.
Results for project PHP master, build date 2015-12-30 06:30:31+02:00
commit: 65e456f
previous commit:8a6f905
revision date: 2015-12-29 23:14:53+01:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
11 matches
Mail list logo