ing real-life work. Don't make sacrifices just to
keep the language simple. Just go "full throttle forward!"
Regards,
Catalin Z. Alexandru
-Original Message-----
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 02, 2008 8:02 PM
To: Marcus Boe
Hi!
My guess is that it allows for development with heavy __autload usage and
then doing deployment based on static analysis where each target page
results in one large php file generated from that analysis. So there won't
be any overhead and each script target would be a single target of its ow
Hello Stanislav,
Tuesday, September 2, 2008, 9:51:38 AM, you wrote:
> Hi!
>> The problem is that the loading/unloading of the scanner and parser can
>> be significant overhead, and by cramming all code into a single file,
>> can result in a 10%-30% performance improvement over code in separate
>
Hi!
The problem is that the loading/unloading of the scanner and parser can
be significant overhead, and by cramming all code into a single file,
can result in a 10%-30% performance improvement over code in separate
files, even with an opcode cache. This has been verified independently
Not on
Hello Gregory,
Sunday, August 31, 2008, 10:04:23 PM, you wrote:
> Lukas Kahwe Smith wrote:
>> Hello all,
>>
>> All the recent discussions about namespaces, have left many of us
>> wondering if our implementation is rock solid or not. However the
>> discussions were not really well organized. Thi
