Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16039 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7675 invoked by uid 1010); 19 Apr 2005 22:40:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 7625 invoked from network); 19 Apr 2005 22:40:36 -0000 Received: from unknown (HELO yahoo.com.cn) (127.0.0.1) by localhost with SMTP; 19 Apr 2005 22:40:36 -0000 X-Host-Fingerprint: 204.11.219.140 lt1.firehawksystems.com Linux 2.4/2.6 Received: from ([204.11.219.140:49018] helo=lt1.firehawksystems.com) by pb1.pair.com (ecelerity 1.2.12rc1 r(5476:5477)) with SMTP id 17/BB-45122-0E885624 for ; Tue, 19 Apr 2005 18:40:32 -0400 Received: from [10.0.0.2] (adsl-68-248-163-153.dsl.ipltin.ameritech.net [68.248.163.153]) (authenticated bits=0) by lt1.firehawksystems.com (8.13.3/8.13.3) with ESMTP id j3JMeDwl014587 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 19 Apr 2005 15:40:15 -0700 In-Reply-To: References: <9362f0145eb08a0ee9f30fb7d14fa905@firehawksystems.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: Content-Transfer-Encoding: 7bit Cc: internals@lists.php.net Date: Tue, 19 Apr 2005 17:40:01 -0500 To: Jani Taskinen X-Mailer: Apple Mail (2.622) X-Virus-Scanned: ClamAV 0.83/842/Tue Apr 19 14:39:01 2005 on lt1 X-Virus-Status: Clean Subject: Re: [PHP-DEV] Allow .cc files for shared extensions From: list@firehawksystems.com ("Brian J. France") I do, but some of our developers have some wacky idea they should be named .cc. I can keep a internal patch if you rather not, figure I would ask just to make sure. Brian On Apr 19, 2005, at 5:12 PM, Jani Taskinen wrote: > Why don't you name the files .cpp like you're supposed to? > > --Jani > > > On Tue, 19 Apr 2005, Brian J. France wrote: > >> Anybody see a problem with this patch that allows .cc files in shared >> extensions. >> >> If not I will check it into all branches.