Hello Lukas,

Saturday, August 13, 2005, 1:34:35 AM, you wrote:

> Marcus Boerger wrote:

>> 11. class operator cleanup
>>   :: static
>>   -> non static
>>   this would allow to do more things like accessing static members/consts
>>   from anywhere a class is allowed etc. (if proposed that before incl.
>>   patch lookup the archieves).

> could you elaborate what you mean with this ..

> currently (some?) "static" calls from within a method will still result 
> in a non static method call ... like parent::fobar()

> are you talking about cleaning this up?

static=static, non-static=non-static and no moe ZEND_ACC_ALLOW_STATIC

> also do you remember my complaints about the fact that static and 
> inheritance dont mix well, since alot of things are done at compile time 
> for performance reasons .. does this also fall into this topic?

well you could make your own oint in disallowing "if() class" or in other
words allow class definitions only in the main block. If then you go for
forward declarations also "class SomeClassName; /* no block after ; */"
you'd gain a bit:

- being able to use upcoming perl 6 compiler namely parrot (if someone
wants to do the work). Full support with upcoming php idl compiler. But
we have to hear about that from the author.

- moving all inheritance to compile time - already a tiny bit of a spead
increase - together with apc or some other cache another bit of a speed
increase.

On the contray you'd loose some flexibilty (not that i'd like it buut
others do) and btw php is the only language in use i knwo of which is
capable of this.

best regards
marcus

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to