Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:27459 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45278 invoked by uid 1010); 15 Jan 2007 18:30:26 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 45263 invoked from network); 15 Jan 2007 18:30:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jan 2007 18:30:26 -0000 Received: from [127.0.0.1] ([127.0.0.1:15218]) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ECSTREAM id 29/46-33655-148CBA54 for ; Mon, 15 Jan 2007 13:30:25 -0500 Authentication-Results: pb1.pair.com header.from=r@roze.lv; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=r@roze.lv; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain roze.lv designates 80.232.169.231 as permitted sender) X-PHP-List-Original-Sender: r@roze.lv X-Host-Fingerprint: 80.232.169.231 kc.118.lv Linux 2.4/2.6 Received: from [80.232.169.231] ([80.232.169.231:33889] helo=kc.118.lv) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9B/55-33655-545CBA54 for ; Mon, 15 Jan 2007 13:17:41 -0500 Received: from wired (unknown [87.246.141.105]) by kc.118.lv (Postfix) with SMTP id D74CA3202DB for ; Mon, 15 Jan 2007 20:17:17 +0200 (EET) Message-ID: <002201c738d1$727eee70$698df657@wired> To: Date: Mon, 15 Jan 2007 20:17:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Subject: include_once From: r@roze.lv ("Reinis Rozitis") Hello, just a quick question - will the include_once() (Optimized require_once() and include_once() by eliminating fopen(3) on second usage. (Dmitry)) optimisation fix in 5.2.0 backported also in PHP 4 tree (in 4.4.5 maybe?) Theoretically speaking (havent checked the default funcs internal changes between 4.x and 5.2) could it be possible to patch 4.x without breaking the rest of the core? rr