Re: [PEPr] Comment on RFC::Coding standard enhancements
| From: | Paul M Jones | Date: | Sun, 09 Mar 2008 21:17:22 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::Coding standard enhancements | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-49351@lists.php.net to get a copy of this message | ||
On Mar 9, 2008, at 10:25 , till wrote:
On Sun, Mar 9, 2008 at 4:02 AM, David Sanders <dsanders@baselinesolutions.com.au> wrote:75 characters is important for non-technical reasons. I'd been intending to blog about this kind of thing anyway, so the discussion on PEAR-Dev has served as a catalyst. <http://paul-m-jones.com/?p=276> -- pmjWhy do you think printing is no issue anymore? Just curious. I print source code sometimes, and I am always glad if it's within the 80-85 range. Of course I can make it "fit to the page" but then it's smaller or something and with the 80-85 I don't have to worry.Like I said, we need a limit, but I always seem to be hitting 85 characters. It'd be nice if it were longer.But my question here is why do we still need 85 characters as the limit? Is it because code might get emailed? We're not living in the 1980's anymore... so viewing and printing don't seem to be an issue.I constantly use "vim" with files side by side or "vimdiff" and when I edit files that have long lines the code becomes pretty unreadable. Having a limit is a very good thing, it keeps the code readable in most configurations.