--
You received this message because you are subscribed to the Google Groups "Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@arduino.cc.
Well said Paul, thank you.
Tom Igoe
--
sent on the go. please forgive any terseness or typos
The net result of unnecessary white space changes is your pull requests are much harder to review, and if accepted, they have a much higher chance of breaking other pending pull requests or patches maintained by 3rd parties. There are indeed many derivatives/forks of Arduino with varying amounts of customization.
If you're thinking of making things optimal, please try to focus on optimizing the amount of human time & attention needed to review your pull request. The fewer lines altered, the better. I know it's tempting and can see valuable to reformat ugly and inconsistent white space. Cleaner & consistently formatted code seems so desirable. But the thing that's in limited supply, which should be the goal of optimization, is the human developer hours to review and maintain the code base. Reformatting white space is terribly wasteful of human developer time, especially when your edits cause other pending pull requests to no longer automatically merge!
Tabs traditionally have always been 8 spaces on a computer, nothing else.
Any other value comes from typewriters. We aren't writing love letters here.
So if you write something new, please use 8 spaces.
--
Tabs traditionally have always been 8 spaces on a computer, nothing else.
Any other value comes from typewriters. We aren't writing love letters here.
So if you write something new, please use 8 spaces.
Wouldn't it be wonderful if appropriate tabs were actually defined in the file, perhaps as a line like
!.!...!...!...!...!...!...!
If your code indents are so deep that you have problems with it, it is time to rethink your code.
--
You received this message because you are subscribed to the Google Groups "Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@arduino.cc.
(do I REALLY need to go on here???)6 ANSI uses 8 space tabs.5. VT100 uses 8 space tabs.4. Linux uses 8 space tabs.3. Unix uses 8 space tabs.Well...2. DOS and CP/M use 8 space tabs.
1: Terminals always use 8 space tabs.
Mac and Win environments set them to four, creating confusion when code was transferred back and forth.
On 04/24/2016 11:21 PM, Andrew Kroll wrote:
(do I REALLY need to go on here???)6 ANSI uses 8 space tabs.5. VT100 uses 8 space tabs.4. Linux uses 8 space tabs.3. Unix uses 8 space tabs.Well...2. DOS and CP/M use 8 space tabs.
1: Terminals always use 8 space tabs.
With the exception of Linux, is seems as if you're saying a variety of technologies that haven't been in widespread use since the end of the 1980s (*) are more relevant....
(*) - Ok, BSD Unix, AIX, Solaris, HP/UX, IRIX & other commercial Unix systems were still widely used well into the 1990s, and some still retain a very tiny sliver of the installed base of computer systems today. Some people still love BSD. There really isn't any need to go on about old systems with very little practical usage today.
--ignore-space-change
option :-) Which is also very useful for reviewing cleaned up indent code.To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@arduino.cc.