Results for project PHP master, build date 2017-06-14 19:36:53-07:00
commit: 3e6c0b7
previous commit:a251d9b
revision date: 2017-06-14 10:42:37+08:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Results for project PHP master, build date 2017-06-14 18:13:14-07:00
commit: a251d9b
previous commit:5c9d6e8
revision date: 2017-06-14 03:29:06+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Den 2017-06-15 kl. 15:34, skrev Fleshgrinder:
On 6/15/2017 3:29 PM, Björn Larsson wrote:
Seems like the constraints on this feature makes it hard to fly, i.e.
1. Not a hackish implementation
2. Non ambiguous syntax
3. Easy to parse & use syntax for the human
HackLang then prioritised 2 & 3 mak
On Do, 2017-06-15 at 08:29 -0400, Sara Golemon wrote:
> On Thu, Jun 15, 2017 at 5:06 AM, Nikita Popov
> wrote:
> >
> > On Tue, Jun 13, 2017 at 8:23 AM, Remi Collet > g> wrote:
> > >
> > > All extensions in php-src are PHP 3.01 Licensed
> > > (libs may, of course, have different license)
> > >
On 6/15/2017 3:29 PM, Björn Larsson wrote:
> Seems like the constraints on this feature makes it hard to fly, i.e.
> 1. Not a hackish implementation
> 2. Non ambiguous syntax
> 3. Easy to parse & use syntax for the human
>
> HackLang then prioritised 2 & 3 making the end-users happy, but
> had to
Den 2017-06-10 kl. 10:05, skrev Björn Larsson:
Den 2017-06-09 kl. 15:44, skrev Sara Golemon:
On Fri, Jun 9, 2017 at 7:23 AM, Björn Larsson
wrote:
If I take the liberty in using the example above on our option list:
1. $someDict->map(fn($v) => $v * 2)->filter(fn($v) => $v % 3);
2. $someDict->m
On 6/13/2017 8:23 AM, Remi Collet wrote:
> Hi,
>
> All extensions in php-src are PHP 3.01 Licensed
> (libs may, of course, have different license)
>
> Is there any strong rule about this ?
> Or is it OK to have a BSD Licensed extension ?
>
> Context: see sodium PR
> https://github.com/php/php-sr
On Do, 2017-06-15 at 11:06 +0200, Nikita Popov wrote:
> On Tue, Jun 13, 2017 at 8:23 AM, Remi Collet
> wrote:
>
> >
> > Hi,
> >
> > All extensions in php-src are PHP 3.01 Licensed
> > (libs may, of course, have different license)
> >
> > Is there any strong rule about this ?
> > Or is it OK to
On Thu, Jun 15, 2017 at 5:06 AM, Nikita Popov wrote:
> On Tue, Jun 13, 2017 at 8:23 AM, Remi Collet wrote:
>> All extensions in php-src are PHP 3.01 Licensed
>> (libs may, of course, have different license)
>>
>> Is there any strong rule about this ?
>> Or is it OK to have a BSD Licensed extensio
On 6/15/2017 11:33 AM, Nikita Popov wrote:
> Hi,
>
> What makes me skeptical about this is the PR that started this discussion:
> https://github.com/php/php-src/pull/2523/files
>
> Documentation sounds nice, but that is not the kind of documentation I
> would like to see or find particularly usef
On Mon, Jun 12, 2017 at 10:48 PM, David Strauss
wrote:
> Despite providing class whitelisting [1] and documentation about warnings
> about security impacts [2], we continue to see vulnerable uses of
> unserialize() in Drupal modules [3] and partially effective attempts to
> mitigate vulnerabiliti
On Thu, Jun 1, 2017 at 9:04 PM, Fleshgrinder wrote:
> Hey guys!
>
> Just finished the very brief Doxygen RFC. Please let me know if you
> require more information in it, I feel that it is sufficient as is,
> since documenting is not rocket science (writing useful documentation
> definitely is, bu
On Tue, Jun 13, 2017 at 8:23 AM, Remi Collet wrote:
> Hi,
>
> All extensions in php-src are PHP 3.01 Licensed
> (libs may, of course, have different license)
>
> Is there any strong rule about this ?
> Or is it OK to have a BSD Licensed extension ?
>
> Context: see sodium PR
> https://github.com/
On 6/1/2017 9:04 PM, Fleshgrinder wrote:
> Hey guys!
>
> Just finished the very brief Doxygen RFC. Please let me know if you
> require more information in it, I feel that it is sufficient as is,
> since documenting is not rocket science (writing useful documentation
> definitely is, but we cannot
14 matches
Mail list logo
