Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29776 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75487 invoked by uid 1010); 25 May 2007 21:59:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75472 invoked from network); 25 May 2007 21:59:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2007 21:59:58 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.114 unknown Windows 2000 SP4, XP SP1 Received: from [63.205.162.114] ([63.205.162.114:6507] helo=us-ex1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/C0-03210-C5C57564 for ; Fri, 25 May 2007 17:59:57 -0400 Received: from [127.0.0.1] ([192.168.16.180]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 May 2007 14:59:53 -0700 Message-ID: <46575C57.6010909@zend.com> Date: Fri, 25 May 2007 14:59:51 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Rasmus Lerdorf CC: Uwe Schindler , 'PHP Internals' References: <4657170E.8060701@zend.com> <46571CCC.4030801@zend.com> <46573710.6070800@lerdorf.com> <46573903.2060204@zend.com> <000001c79f12$9b6650b0$0201a8c0@VEGA> <465756D4.1080604@lerdorf.com> In-Reply-To: <465756D4.1080604@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 May 2007 21:59:53.0737 (UTC) FILETIME=[06514790:01C79F18] Subject: Re: [PHP-DEV] TSRM changes broke windows compile From: stas@zend.com (Stanislav Malyshev) > quite expensive. And SAPI isn't only for web server interaction. SAPI > is a general-purpose abstraction API that sits between PHP and anything > PHP talks to. CGI, CLI, and even embedded PHP are all SAPI-driven. > There is no way to use PHP without at least a stub SAPI layer. There is, however, a way to use Zend Engine/TSRM. With this change, Zend Engine/TSRM could no longer be used without PHP. And all this for some time() patch... > That could be done, yes. I'm just not sure it is worth the complexity. I, for one, don't really understand what all this filesystem stuff does in TSRM anyway. It's not like it has anything to do with thread safety. Maybe it should just be moved to PHP and Zend Engine should talk to it via handlers? > TSRM is obviously a PHP-specific thing and it is already somewhat > SAPI-dependant even without this. The THREAD_T and MUTEX_T definitions > change based on the chosen SAPI. It doesn't explicitly include SAPI.h No, it's not SAPI-dependent. It's environment-dependent, which is entirely different thing. It can be configured, built and used without PHP. > because it relies on the side-effect of TSRM.h being included after the > SAPI stuff. I don't see an explicit include as really changing things > very much. It does. Now it's impossible to use TSRM without PHP and it also doesn't build on Windows. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/