Le 10/11/2015 04:30, Bob Weinand a écrit :
Quoting the valgrind 3.8.0 release notes:
Specifically,
--vex-iropt-precise-memory-exns has been removed and replaced by
--vex-iropt-register-updates, with extended functionality.
so, I'll need to update it… may you please verify if
--vex-iropt-
> Am 10.11.2015 um 04:11 schrieb François Laupretre :
>
> Hi Bob,
>
> I'm currently testing a new PHP extension on travis-ci in valgrind/leak_check
> mode. In PHP 5 environments, it is OK but, on PHP 7, every test fails with
> this message :
>
> valgrind: Bad option: --vex-iropt-register-updat
Hey Dan,
On 9 November 2015 at 23:24, Dan Ackroyd wrote:
> Hi Reeze,
>
> On 9 November 2015 at 13:35, reeze wrote:
> > Hi internals!
> >
> > I'd like to open a discussion on the RFC to allow set default values for
> > list() assignment: https://wiki.php.net/rfc/list_default_value.
> >
> > What
Hi Bob,
I'm currently testing a new PHP extension on travis-ci in
valgrind/leak_check mode. In PHP 5 environments, it is OK but, on PHP 7,
every test fails with this message :
valgrind: Bad option: --vex-iropt-register-updates=allregs-at-mem-access
valgrind version is 3.7.0.
For a full log,
On 11/09/2015 04:20 PM, David Zuelke wrote:
> November 30 is Cyber Monday, where people are either
>
> a) focused on maxing out their credit cards on every possible e-commerce
> site, or
> b) unable to roll out PHP 7 because their customers are busy with a)
>
> At least at Heroku we have a black
Hi!
> November 30 is Cyber Monday, where people are either
>
> a) focused on maxing out their credit cards on every possible
> e-commerce site, or b) unable to roll out PHP 7 because their
> customers are busy with a)
>
> At least at Heroku we have a blackout policy around Thanksgiving and
> Chr
November 30 is Cyber Monday, where people are either
a) focused on maxing out their credit cards on every possible e-commerce site,
or
b) unable to roll out PHP 7 because their customers are busy with a)
At least at Heroku we have a blackout policy around Thanksgiving and Christmas
for platform
On 9 November 2015 at 13:46, Derick Rethans wrote:
> On Thu, 5 Nov 2015, Niklas Keller wrote:
>
>> I discovered today that anonymous class names contain a null byte
>> right after "class@anonymous". I don't think class names should
>> contain non-printable characters.
>>
>> How about removing that
On Thu, 5 Nov 2015, Niklas Keller wrote:
> I discovered today that anonymous class names contain a null byte
> right after "class@anonymous". I don't think class names should
> contain non-printable characters.
>
> How about removing that null byte?
I would suggest replacing it with something
I love that The PHP Development Team is not looking to rush a release and
while I, like many others wish to see PHP 7.0 I would rather have a stable
and solid release over the idea of a rushed release. So I commend the
choice of releasing another RC (RC7) coming up in the next few days
There appe
On Mon, Nov 9, 2015 at 8:50 PM, Andi Gutmans wrote:
>> On Nov 8, 2015, at 5:35 PM, Rasmus Lerdorf wrote:
>>
>> On 11/08/2015 05:16 PM, Anatol Belski wrote:
>>> Exactly, the relevant patches are going into RC7 which is then out on 12th
>>> instead of GA. The next closest release slot were then Nov
> On Nov 8, 2015, at 5:35 PM, Rasmus Lerdorf wrote:
>
> On 11/08/2015 05:16 PM, Anatol Belski wrote:
>> Exactly, the relevant patches are going into RC7 which is then out on 12th
>> instead of GA. The next closest release slot were then Nov 26th, either for
>> GA or for RC8 (but better not try to
2015-11-09 17:46 GMT+01:00 Leigh :
>
> On 9 November 2015 at 16:42, Niklas Keller wrote:
>
>>
>> Having the path info is quite useful for debugging purposes.
>>
>> Regards, Niklas
>>
>
> It is, but it will always still be available from
> ReflectionClass::getFileName()
>
But most implementations
Good job! Well done for the revival. Well written, well reasoned, all
around good job.
Keep making PHP awesome, just in case I have to use it again sometime. xD
On Sun, Nov 8, 2015 at 7:24 PM, Andrea Faulds wrote:
> Hi everyone,
>
> Voting on the Void Return Type RFC commenced on 2015-10-29 and
On 9 November 2015 at 15:27, Steven Hilder
>
>
> So, I prepared a patch for `get_class()` and `ReflectionClass::getName()`,
> which in my view should behave the same way as `var_dump()` etc., but I've
> now realised that ignoring the unique suffix from the class name will break
> functionality that
On 9 November 2015 at 16:42, Niklas Keller wrote:
>
> Having the path info is quite useful for debugging purposes.
>
> Regards, Niklas
>
It is, but it will always still be available from
ReflectionClass::getFileName()
2015-11-09 16:27 GMT+01:00 Steven Hilder <
steven.hilder@sevenpercent.solutions>:
> On Thu, 05 Nov 2015 15:14:47, Leigh wrote:
>
>> On 5 November 2015 at 14:59, Rowan Collins
>> wrote:
>>
>>> PHP uses null bytes quite a lot to produce deliberately illegal
>>> identifiers. For instance the old ev
On 6 November 2015 at 00:08, François Laupretre wrote:
> Hi,
>
> An uninitialized HashTable generally is
> filled with 0s. Today, using an uninitialized HashTable goes undetected,
> even in debug mode (because HT_OK == 0), and is very hard to track.
Uninitialized variables should be pretty easy t
On Thu, 05 Nov 2015 15:14:47, Leigh wrote:
On 5 November 2015 at 14:59, Rowan Collins
wrote:
PHP uses null bytes quite a lot to produce deliberately illegal
identifiers. For instance the old eval-like create_function() [e.g.
https://3v4l.org/hqHjh] and the serialization of private members [e.g
Hi Reeze,
On 9 November 2015 at 13:35, reeze wrote:
> Hi internals!
>
> I'd like to open a discussion on the RFC to allow set default values for
> list() assignment: https://wiki.php.net/rfc/list_default_value.
>
> What is your idea?
I find the list construct to be quite magic already. Isn't it
Results for project PHP master, build date 2015-11-09 05:25:44+02:00
commit: 7345dde792860d92cc86c19caa3a20737dcf567e
revision date: 2015-11-07 23:06:47-08:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping
2, LLC 45 MB
mem
Hi internals!
I'd like to open a discussion on the RFC to allow set default values for
list() assignment: https://wiki.php.net/rfc/list_default_value.
What is your idea?
Thanks.
--
Reeze Xia
http://reeze.cn
On 11/08/2015 02:45 PM, Stanislav Malyshev wrote:
I think this is the right thing to do, we can wait for a bit if it means
better stability.
+1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Rasmus,
> -Original Message-
> From: Rasmus Lerdorf [mailto:ras...@lerdorf.com]
> Sent: Monday, November 9, 2015 2:36 AM
> To: Anatol Belski ; 'Stanislav Malyshev'
> ; internals@lists.php.net
> Cc: 'Kalle Sommer Nielsen' ; 'Ferenc Kovacs'
> Subject: Re: [PHP-DEV] PHP 7 RTM date
>
> On
24 matches
Mail list logo
