Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64315 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12775 invoked from network); 16 Dec 2012 23:48:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2012 23:48:04 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.210.42 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.210.42 mail-da0-f42.google.com Received: from [209.85.210.42] ([209.85.210.42:63352] helo=mail-da0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/CE-27715-2BD5EC05 for ; Sun, 16 Dec 2012 18:48:03 -0500 Received: by mail-da0-f42.google.com with SMTP id z17so2291212dal.29 for ; Sun, 16 Dec 2012 15:47:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=78IjgOJwxcSq7yGARRvpNEmxUcoPYnTqFIr8Ril9XuE=; b=ihfI2aMiUflAQlxDLKo+XAq7p7yHwY3UR+3a49hZNVKn9ZHrwtDvHekUFl0gB6/wRu bophbkVSCck6xgZbzqojPsK3Yo3sNsFtQOv2L8X+qrrwbcQLzkYGgywE57YF8Jqp6Ccm QpPhGMrisDlsFBO2FM1EwCF71GX2oe0rP9CwHR0Z8ZpwP97lIJgm6fhbttwqwPmwk4UX yrJcHB0ZR/ROFyvGBtHh/wgR05iYB7TW8B3KFQb/5SmDarSsCbezmIu05xASW1z6vgsW KTOdgGNctd6QmRhcDhouJveDAAYN1nrdjqi3zZU/71JxlqY2tYhTL/LWIXXIiNTuIYje tfRw== Received: by 10.68.244.233 with SMTP id xj9mr38398056pbc.167.1355701674927; Sun, 16 Dec 2012 15:47:54 -0800 (PST) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id rq7sm7045081pbc.69.2012.12.16.15.47.53 (version=SSLv3 cipher=OTHER); Sun, 16 Dec 2012 15:47:54 -0800 (PST) Message-ID: <50CE5DA9.4060706@lerdorf.com> Date: Sun, 16 Dec 2012 15:47:53 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Lester Caine CC: PHP internals References: <50CDDA20.8090400@lsces.co.uk> <50CE252D.5060305@lsces.co.uk> <50CE2ECB.5030804@lsces.co.uk> <50CE3197.90403@lerdorf.com> <50CE572C.50305@lsces.co.uk> In-Reply-To: <50CE572C.50305@lsces.co.uk> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkCGvYx6oeICUnADRw3oW3mH+TuFgsZdHJAzPMSwd0eyxtep62/qzLS9zk2+MpTJ0FNcsCE Subject: Re: [PHP-DEV] Core liason for PHP FIG From: rasmus@lerdorf.com (Rasmus Lerdorf) On 12/16/2012 03:20 PM, Lester Caine wrote: > One gets the impression that it's all too late, so from the other side, > should all of the core files be changed to follow the new de-facto > standard? And YES I classify using different white space standards for > different file formats as more of a problem! Writing files in one format > which are then used to create files for a different format is a recipe > for confusion? It's bad enough trying to get EOL right between OS's > without adding 'what tab standard are you using' :( The core coding standards will not change regardless of what some outside group says, nor do I expect any other project to change their standards. -Rasmus