Hi Christopher,
Christopher Jones wrote:
Dmitry Stogov wrote:
> Hi,
>
> I've added the corresponding patch for APC, so anyone is able to verify
> the performance difference.
>
> http://wiki.php.net/rfc/performanceimprovements
Dmitry,
What do you think caused the "fw" difference in abso
On Tue, 13 Apr 2010, Dmitry Stogov wrote:
> I've published all the patches, their description and performance evaluation
> at http://wiki.php.net/rfc/performanceimprovements
I've a few questions and comments:
http://wiki.php.net/rfc/performanceimprovements#zend_engine_vm_tuning
You're writing t
Am 20.04.2010 09:21, schrieb Derick Rethans:
> You're writing that the ZEND_CATCH opcode has to be used with a constant
> class name, so how would "catch ( self $e )" be represented in op-codes
> now?
Is self not replaced with the class name at compile time? And why would
you write such code?
Hi Derick,
Thank you for review.
Derick Rethans wrote:
On Tue, 13 Apr 2010, Dmitry Stogov wrote:
I've published all the patches, their description and performance evaluation
at http://wiki.php.net/rfc/performanceimprovements
I've a few questions and comments:
http://wiki.php.net/rfc/perfor
Hi,
Also $this have been wildly discuss here, but the same discussion can be
apply to static/self.
self might be simple to figure out how to bind within a closure.
It can be bind to the name of the class where the closure is define.
static is a more tricky one but it should be the same thing
On Tue, 20 Apr 2010, Dmitry Stogov wrote:
> Derick Rethans wrote:
> > On Tue, 13 Apr 2010, Dmitry Stogov wrote:
> >
> > > I've published all the patches, their description and performance
> > > evaluation
> > > at http://wiki.php.net/rfc/performanceimprovements
> >
> > I've a few questions and c
On 20.04.2010 12:41, Derick Rethans wrote:
>>> You're writing that the ZEND_CATCH opcode has to be used with a constant
>>> class name, so how would "catch ( self $e )" be represented in op-codes now?
>>
>> I dropped such possibility. Does someone use it?
>> For me it looks useless. If it's really
Jordi Boggiano wrote:
On 20.04.2010 12:41, Derick Rethans wrote:
You're writing that the ZEND_CATCH opcode has to be used with a constant
class name, so how would "catch ( self $e )" be represented in op-codes now?
I dropped such possibility. Does someone use it?
For me it looks useless. If i
hi,
thank you for reading my suggestion, and now I hope that PHP_FPM can
add process control to prevent from system memory running out.
There are many ways to do this, my patch is to check the PHP heap memory,
this is very easy. We can also control the child process's life time, all I
need
is t
Hi everyone,
Regarding some of the features that are going to ship in PHP 6, I'm going to
take some liberty and make some personal remarks in the form of positive
criticism.
1. SYSTEM NAMESPACES. There are many PHP built-in functions that act on
certain groups of entities. The best examples are t
On Tue, Apr 20, 2010 at 05:39:07PM +0300, Adi Nita wrote:
> Hi everyone,
>
> Regarding some of the features that are going to ship in PHP 6, I'm going to
> take some liberty and make some personal remarks in the form of positive
> criticism.
>
> 1. SYSTEM NAMESPACES. There are many PHP built-in f
Hi!
Also $this have been wildly discuss here, but the same discussion can be
apply to static/self.
self might be simple to figure out how to bind within a closure.
It can be bind to the name of the class where the closure is define.
I would guess self binds to the scope, and static binds to t
Hi!
I checked bug 50688: http://bugs.php.net/bug.php?id=50688
And discovered that the problem there stems form teh fact that for some
reason exception when assembling the backtrace uses
SEPARATE_ZVAL_TO_MAKE_IS_REF() - i.e. the agrs are put in the backtrace
as refs.
Does anybody have an ide
On 2010-04-20 16:39:07 +0200, Adi Nita said:
Hi everyone,
Regarding some of the features that are going to ship in PHP 6, I'm going to
take some liberty and make some personal remarks in the form of positive
criticism.
1. SYSTEM NAMESPACES.
I prefer see scalar object implemented with all grou
Hi!
1. SYSTEM NAMESPACES. There are many PHP built-in functions that act on
certain groups of entities. The best examples are the *array_** and
*str* *functions.
There are many of them, and it gets really cumbersome to repeat the same
prefix for each and every one. This is clearly a reminiscence
On 20/04/2010 15:39, Adi Nita wrote:
Hi everyone,
[...]
Thank you for your time,
Adrian Nita
The PHP-way is to NEVER BREAK BC!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Apr 21, 2010 at 7:29 AM, Mark Skilbeck wrote:
> On 20/04/2010 15:39, Adi Nita wrote:
>
>> Hi everyone,
>>
>> [...]
>>
>>
>> Thank you for your time,
>>
>> Adrian Nita
>>
>>
> The PHP-way is to NEVER BREAK BC!
>
>
Except when you can do some cool stuff, or you are a lazy dev, and easier to
17 matches
Mail list logo
