Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57076 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46416 invoked from network); 24 Dec 2011 11:18:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Dec 2011 11:18:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=kassner@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kassner@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: kassner@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-ww0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:52846] helo=mail-ww0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/69-16446-125B5FE4 for ; Sat, 24 Dec 2011 06:18:58 -0500 Received: by wgbds13 with SMTP id ds13so14050142wgb.5 for ; Sat, 24 Dec 2011 03:18:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=rTcxK6CY9d3cL+iP0ql1TC7P6buHNplxUmhmezpV/Oo=; b=cJ0gtvG6vmXfP+089buy1yuDw1/P/TmnPxdHp0HEUB7POwKwKBKnv0DmbZDtk0kUdj xN5+Rma9byqxkUHGjYkTaBfTt3jpq4NVdBfc61YErpdL3ZAtohS4sPAnSFJS9OQ63GZP 5eyoRk8VlR2BRZbAwnmEsjrZdHCx7g1EnR420= Received: by 10.216.136.74 with SMTP id v52mr15891764wei.13.1324725534270; Sat, 24 Dec 2011 03:18:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.105.212 with HTTP; Sat, 24 Dec 2011 03:18:33 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Dec 2011 09:18:33 -0200 Message-ID: To: Pierre Joye Cc: Laruence , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [Proposal] Remove the tail ws in codes From: kassner@gmail.com (Rafael Kassner) Oh, shame on my, I was thinking about PHP code. Even so, this is coding standards for PHP C code. Have we this? This can be a good one. On Sat, Dec 24, 2011 at 9:11 AM, Pierre Joye wrote: > hi! > > Laruence refers to the PHP C source code and removing trailing white > spaces is a good thing as it is part of our CS. > > Go ahead Laruence :) > > On Sat, Dec 24, 2011 at 12:09 PM, Rafael Kassner wrot= e: >> AFAIK, PHP files are transformed in bytecode before the execution, so >> white spaces will not interfere in nothing except more time to >> transfer the file over SFTP. >> >> It's pretty good to implement on our IDEs (and a lot of them is doing >> it), once trailing white spaces are annoying while we are developing. >> >> On Sat, Dec 24, 2011 at 4:21 AM, Laruence wrote: >>> Hi: >>> =A0 =A0I noted there are a lot of tail white spaces in our codes, >>> >>> =A0 =A0it is better to remove them all, =A0and we also should watch suc= h ws >>> in furture. >>> >>> =A0 =A0a simple way to erase such ws in vim, use :%s /\s\+$//g >>> >>> thanks >>> >>> -- >>> Laruence =A0Xinchen Hui >>> http://www.laruence.com/ >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >> >> >> >> -- >> Atenciosamente, >> Rafael Kassner >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> > > > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --=20 Atenciosamente, Rafael Kassner