https://wiki.iotivity.org/iotivity_coding_standards already has requirements around lack of tabs so this is not about a ?spaces vs. tabs? discussion, not sure where you got that idea. This is about using uncrustify to generate consistent spacing throughout code, so that devs don?t have to, and so we stop seeing many different styles mixed within the same file making it hard to read. As mentioned earlier, other OSS projects use it within jenkins and we?ve found it helps readability significantly.
From: Gregg Reynolds [mailto:[email protected]] Sent: Sunday, June 26, 2016 5:56 PM To: Dave Thaler <dthaler at microsoft.com> Cc: Bell, Richard S <richard.s.bell at intel.com>; Macieira, Thiago <thiago.macieira at intel.com>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] uncrustify On Sun, Jun 26, 2016 at 7:45 PM, Dave Thaler via iotivity-dev <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> wrote: Yes there is an IoTivity wiki coding standards page but it does not have sufficient precision. For example, it only mentions not to use tabs, it contains little or no guidance about other forms of whitespace consistency. That's why I'm proposing we mandate/automate use of uncrustify. Just to be clear: we are now engaged a discussion of spaces v. tabs. Is that correct? Did I misread? Have I lost my mind? VERY sincerely, Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160627/c1b39fc9/attachment.html>
