Newsgroups: php.apc.dev,php.internals Path: news.php.net Xref: news.php.net php.apc.dev:194 php.internals:43188 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28224 invoked from network); 26 Feb 2009 19:06:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2009 19:06:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 204.11.219.139 mail.lerdorf.com Received: from [204.11.219.139] ([204.11.219.139:47505] helo=mail.lerdorf.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E2/CC-30584-618E6A94 for ; Thu, 26 Feb 2009 14:06:00 -0500 Received: from trainburn-lm.corp.yahoo.com (trainburn-lm.corp.yahoo.com [207.126.233.11]) (authenticated bits=0) by mail.lerdorf.com (8.14.3/8.14.3/Debian-6) with ESMTP id n1QJ5t9J020290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 26 Feb 2009 11:05:56 -0800 Message-ID: <49A6E813.4030900@lerdorf.com> Date: Thu, 26 Feb 2009 11:05:55 -0800 User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: shire CC: Gopal V , PHP Internals List , apc-dev@lists.php.net References: <49A097FE.10205@tekrat.com> <49A6A82C.9030504@yahoo-inc.com> <49A6C4D1.2060706@lerdorf.com> <49A6E6C8.90801@tekrat.com> In-Reply-To: <49A6E6C8.90801@tekrat.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [APC-DEV] [RFC] APC/PHP Lazy Loading From: rasmus@lerdorf.com (Rasmus Lerdorf) shire wrote: > I agree for the general case, in our development environment though this > might cause some pains. But we could always start there and see how it > goes. I agree that Xdebug isn't really a use case we always need to > optimize for. Is it ever a case we need to optimize for? If you are running xdebug, you aren't worried about execution speed. You certainly aren't going to be running your PHP under xdebug in any sort of production environment. -Rasmus