Stut wrote:
> Jochem Maas wrote:
>> Stut wrote:
>>> Jo chem baas wrote:
^- wtf happened here? :-) it's quite funny if you know dutch :-)
...
>>> Whether there is conditional definition or not, the opcode cache will
>>> look the same. The reason for this is that function and class
>>> definitions happen at runtime not compile time. This would have to be
>>> the case for conditional definition to work at all, since the compiler
>>> cannot determine the value of a condition at compile-time.
>>
>> okay, but I was just paraphrasing the man Rasmus, although I admit I may
>> have misinterpreted (or misundersstood the 'why') - thought I pretty sure
>> he has written on a number of occasions that code like the following
>> sucks
>> for op-code caches and should be avoided:
>>
>> if (foo()) {
>> class Foo { }
>> }
>
> Hopefully he's reading and will be able to give us a definitive answer.
here is the post that I was recalling:
http://lists.nyphp.org/pipermail/talk/2006-March/017676.html
I believe his third point validates what I was saying although I did
make a bit of a mess with regard of my use of terminology.
>
> I'm going by my experience of stepping through code with Zend Studio,
> but it's possible (probably likely) that ZE does something slightly
> different when a debugger is attached.
>
> -Stut
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
