Am 29.10.15 um 01:44 schrieb Bob Weinand:
>> Am 29.10.2015 um 01:08 schrieb Andrea Faulds :
>>
>> Hi everyone,
>>
>> It’s been two weeks, so voting on this RFC can start. The rules are as
>> usual. This is a language change, so a 2/3 majority is required.
>>
>> The vote can be found here:
>>
>> ht
I've fixed few issues reported by Bob.
On Wed, Oct 28, 2015 at 11:35 PM, Dmitry Stogov wrote:
> Hi,
>
> Please review the PR (for master only).
> It adds an API call to get information about opcode operand and
> extended_value meaning. This API should be useful for phpdbg, xdebug and
> others.
>
Hi,
Welcome back, Andrea! It's great to see you contributing here again :)
2015-10-28 21:08 GMT-03:00 Andrea Faulds :
> Hi everyone,
>
> It’s been two weeks, so voting on this RFC can start. The rules are as
> usual. This is a language change, so a 2/3 majority is required.
>
> The vote can be fo
Hi internals!
I want to revive an old patch I was working on last year, and open for
discussion the last missing piece to make it fully complete, allowing me to
write a RFC.
Link to patch introducing support to private classes:
https://github.com/php/php-src/pull/947
Currently, there's no way to
On Wed, Oct 28, 2015 at 8:17 PM, François Laupretre wrote:
> Hi Andrea,
>
> Le 29/10/2015 01:08, Andrea Faulds a écrit :
>>
>>
>> The vote can be found here:
>>
>> https://wiki.php.net/rfc/void_return_type#vote
>
>
> Just voted +1 as, unlike some :), I like the idea of distinguishing void
> from n
Hi Andrea,
Le 29/10/2015 01:08, Andrea Faulds a écrit :
The vote can be found here:
https://wiki.php.net/rfc/void_return_type#vote
Just voted +1 as, unlike some :), I like the idea of distinguishing void
from null.
Is it too late to add a note in the RFC, listing the possibility, in the
Hi Andrea,
On Oct 28, 2015 9:06 PM, "Andrea Faulds" wrote:
>
> Hi Dmitry,
>
>
> Dmitry Stogov wrote:
>>
>> Please take a look: https://github.com/php/php-src/pull/1604
>> The speed improvement on real-life is insignificant.
>> VM size is increased by 10KB.
>>
>> I don't have a strong opinion, if
> Am 29.10.2015 um 01:08 schrieb Andrea Faulds :
>
> Hi everyone,
>
> Its been two weeks, so voting on this RFC can start. The rules are as usual.
> This is a language change, so a 2/3 majority is required.
>
> The vote can be found here:
>
> https://wiki.php.net/rfc/void_return_type#vote
>
Hi again,
Andrea Faulds wrote:
Voting starts today (2015-10-28) and will end next Sunday (2015-11-08),
10 days time.
My apologies, that should say today is the 29th, not the 28th, so
2015-10-29. Unfortunately I lost my glasses when I went to PHP North
West this year, and I'd procrastinated
Hi everyone,
Its been two weeks, so voting on this RFC can start. The rules are as
usual. This is a language change, so a 2/3 majority is required.
The vote can be found here:
https://wiki.php.net/rfc/void_return_type#vote
Voting starts today (2015-10-28) and will end next Sunday (2015-11-0
On Wed, 2015-10-28 at 16:02 +0100, Erik van Velzen wrote:
> I didn't see how it could be generalized but your example clears that up.
Quick attempt of a generalization:
abstract class AbstractRAIIGuard {
private $succeeded = false;
protected abstract function fail();
protected funct
On Wed, 2015-10-28 at 16:45 +, Rowan Collins wrote:
> On the downside, it's worth noting that while PHP destructors are
> technically deterministic, the language can actually prevent them
> running on scope exit, because Exceptions hold references to everything
> used as a parameter in their
> -Original Message-
> From: Leigh [mailto:lei...@gmail.com]
> Sent: Wednesday, October 28, 2015 11:14 PM
> To: Anatol Belski
> Cc: php-...@lists.php.net; PHP Internals
> Subject: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] com php-src: Remove
> arc4random: ext/standard/config.m4 ext/standard
On 28 October 2015 at 09:51, Anatol Belski wrote:
> Yeah, I was only talking about those two OS versions that are known for
> sure to have proper implementations. Even that is a smaller community than
> fe Linux, IMHO no reason to handicap users, especially as the corresponding
> codes are presen
Hi,
Please review the PR (for master only).
It adds an API call to get information about opcode operand and
extended_value meaning. This API should be useful for phpdbg, xdebug and
others.
Once these extension switch to new API, they will support most new opcodes
out of the box.
https://github.co
wrapping the service container code that is triggering this bug with
gc_disable() and gc_enable() or calling gc_collect_cycles() before its run
seems to "fix" the segfault which seems to suggests a garbage collection
problem.
On Wed, Oct 28, 2015 at 12:13 PM James Gilliland
wrote:
> So in an eff
Hi Dmitry,
Dmitry Stogov wrote:
Please take a look: https://github.com/php/php-src/pull/1604
The speed improvement on real-life is insignificant.
VM size is increased by 10KB.
I don't have a strong opinion, if this should go into master or not.
10KB VM size increase for insignificant real-lif
So in an effort to fully support PHP 7 out of the box with the eminent
release of Drupal 8, we're trying to track down some segmentation faults in
our testing infrastructure. One that seems to be causing a lot of failures
is listed here.
https://bugs.php.net/bug.php?id=70805
Does anyone have any
Erik van Velzen wrote on 28/10/2015 15:02:
The ScopeGuard's destructor can now detect the condition:
if ( $this->success_registered ) {
// Function reached checkpoint for this scope
$this->callSuccessHandlers();
} else {
// Function aborted early, due to a throw or early return
$
Results for project PHP master, build date 2015-10-28 16:24:19+02:00
commit: ff0ec065623a7563cc9a99586a9cb2f351f3cbfa
revision date: 2015-10-28 12:56:26+01:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping
2, LLC 45 MB
mem
I didn't see how it could be generalized but your example clears that up.
- Erik
2015-10-28 15:40 GMT+01:00 Rowan Collins :
>
> Did you see Johannes' suggestion re explicit success vs implicit failure?
>
> $scope = new ScopeGuard;
>
> $scope->onSucces(function() { logTransactionOne(); });
> $scop
Erik van Velzen wrote on 28/10/2015 13:28:
try {
$scope = new ScopeGuard;
$scope->onSucces(function() { logTransactionOne(); });
$scope->onFailure(function() { rollbackTransationOne(); });
doTransactionOne();
$scope->onSuccess(function() { logTr
Hi Erik,
On Wed, 28 Oct 2015 16:28:59 +0300, Erik van Velzen wrote:
Thanks for your input.
I did not try-catch because it doesn't really work, you either
duplicate rollback code or get excessive nesting. Real code will
obviously be more complicated than the examples.
Also in both cases the ha
Thanks for your input.
I did not try-catch because it doesn't really work, you either
duplicate rollback code or get excessive nesting. Real code will
obviously be more complicated than the examples.
Also in both cases the handlers are many lines apart from the actual
transaction call.
Duplicate
On Wed, 2015-10-28 at 11:00 +0100, Erik van Velzen wrote:
> Subject says it all.
>
> I want to make a small "ScopeGuard" library for exception-safe
> transactions, like the following:
>
> $scope = new ScopeGuard;
>
> $scope->onSucces(function() { logTransactionOne(); });
> $scope->on
Subject says it all.
I want to make a small "ScopeGuard" library for exception-safe
transactions, like the following:
$scope = new ScopeGuard;
$scope->onSucces(function() { logTransactionOne(); });
$scope->onFailure(function() { rollbackTransationOne(); });
doTransactionOne();
Hi Leigh,
> -Original Message-
> From: Leigh [mailto:lei...@gmail.com]
> Sent: Tuesday, October 27, 2015 10:37 AM
> To: Anatol Belski
> Cc: Leigh ; php-...@lists.php.net; PHP Internals
>
> Subject: [PHP-DEV] Re: [PHP-CVS] com php-src: Remove arc4random:
> ext/standard/config.m4 ext/stand
27 matches
Mail list logo
