Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57403 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82283 invoked from network); 17 Jan 2012 22:21:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2012 22:21:55 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:53875] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7F/73-59894-184F51F4 for ; Tue, 17 Jan 2012 17:21:54 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id DD3AB270713 for ; Tue, 17 Jan 2012 17:21:50 -0500 (EST) X-Virus-Scanned: OK Received: by smtp6.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AC37F2706F2 for ; Tue, 17 Jan 2012 17:21:50 -0500 (EST) Message-ID: <4F15F47E.6030501@sugarcrm.com> Date: Tue, 17 Jan 2012 14:21:50 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reflection to remove final From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > This doesn't seem right. Correct me if I'm wrong: for internal classes, > their data structures are allocated permanently, so I'd say the effects of > removing the flag would be permanent (i.e., would affect subsequent > requests). And for threaded builds this could cause races between the > threads. It'd probably also mess up bytecode caches, since they permanently store class definitions. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227