After much thinking regarding array in immutable objects I'm thinking of
revoking this RFC. If someone has some suggestion on that matter now is the
time, but otherwise my work is done on this one.
Cheers,
2016-12-12 20:56 GMT+01:00 Paul Jones :
>
> > On Dec 12, 2016, at 13:36, Andrea Faulds wr
Hello,
On 13.12.16 10:17, Silvio Marijić wrote:
> After much thinking regarding array in immutable objects I'm thinking of
> revoking this RFC. If someone has some suggestion on that matter now is the
> time, but otherwise my work is done on this one.
It would be nice if you could summarize the f
OpenSSL support for 1.0.1 will end this year.
Support for version 1.0.1 will cease on 2016-12-31. No further releases of
> 1.0.1 will be made after that date. Security fixes only will be applied to
> 1.0.1 until then.
> Version 1.0.0 is no longer supported.
> Version 0.9.8 is no longer supported.
Morning,
Can you please update the RFC with the dates that voting started and will
end, so that anyone browsing knows when the deadline for decision is
without trawling through internals.
Cheers
Joe
On Fri, Dec 9, 2016 at 9:36 AM, Matteo Beccati wrote:
> Hi Guilherme,
>
> it's not really a new
*Disclaimer*
Sorry if this has been discussed before, i tried searching, but i couldn't
find much information.
I probably have nowhere near the experience of you guys, so i apologize if
i overlooked something obvious. I'd like to hear if this is a good or a
terrible idea and the reasons behind it.
On 29 February 2016 at 07:43, Dmitry Stogov wrote:
> I think the most clear way is to apply the new $offset argument and then the
> old way to skip first bytes of input string.
> So unpack("@$skip/N4", $message, $offset) will skip $offset+$skip.
> Actually, this is the way how the proposed patch
On 13 December 2016 13:38:53 GMT+00:00, "Dejan Stošić"
wrote:
>*Disclaimer*
>Sorry if this has been discussed before, i tried searching, but i
>couldn't
>find much information.
It has, quite often actually. Here's a few threads I found in a quick search
that look relevant:
https://marc.info/?t=
On 12/13/2016 07:38 AM, Dejan Stošić wrote:
*Disclaimer*
Sorry if this has been discussed before, i tried searching, but i couldn't
find much information.
I probably have nowhere near the experience of you guys, so i apologize if
i overlooked something obvious. I'd like to hear if this is a good
On 12/13/2016 02:31 AM, Niklas Keller wrote:
OpenSSL support for 1.0.1 will end this year.
Support for version 1.0.1 will cease on 2016-12-31. No further releases of
1.0.1 will be made after that date. Security fixes only will be applied to
1.0.1 until then.
Version 1.0.0 is no longer supported
Results for project PHP master, build date 2016-12-12 20:29:17-08:00
commit: 675fc9e
previous commit:32201fe
revision date: 2016-12-12 22:00:30+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Am 13.12.2016 14:45 schrieb "Dejan Stošić" :
*The problem*
Currently, PHP will parse the incoming HTTP request body only for GET
requests (and store the data in superglobal $_GET) and for POST requests
(and store the data in $_POST).
Additionally it will parse the data only for
*application/x-ww
On Tue, Dec 13, 2016 at 10:31 AM, Niklas Keller wrote:
> OpenSSL support for 1.0.1 will end this year.
>
> Support for version 1.0.1 will cease on 2016-12-31. No further releases of
>> 1.0.1 will be made after that date. Security fixes only will be applied to
>> 1.0.1 until then.
>> Version 1.0.0
On 13.12.2016, at 11:31, Niklas Keller wrote:
>
> OpenSSL support for 1.0.1 will end this year.
>
> Support for version 1.0.1 will cease on 2016-12-31. No further releases of
>> 1.0.1 will be made after that date. Security fixes only will be applied to
>> 1.0.1 until then.
>> Version 1.0.0 is no
13 matches
Mail list logo
