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 <pierre....@gmail.com> 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 <kass...@gmail.com> wrote: >> 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 <larue...@php.net> wrote: >>> Hi: >>> I noted there are a lot of tail white spaces in our codes, >>> >>> it is better to remove them all, and we also should watch such ws >>> in furture. >>> >>> a simple way to erase such ws in vim, use :%s /\s\+$//g >>> >>> thanks >>> >>> -- >>> Laruence Xinchen 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 -- Atenciosamente, Rafael Kassner -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
