[Xastir-dev] Proposal to change project coding standards: Please vote!

[Chris Bell]

1) 2 character, space
2) Line up braces vertically
3) Include braces when optional

Chris.
AF6ZV (formerly KD6ZWR)


On Wed, May 1, 2019 at 1:01 PM KF4LVZ <kf4lvz at acarver.net> wrote:

> On 2019-05-01 09:58, Curt Mills wrote:
> > Please don't be shy about voting! There are 118 people on the Xastir-dev
> > list and I've only seen 3 votes, including my own.
> >
> > If you're a C-coder and have an reasoned opinion we'd like to hear it and
> > see your vote. Anyone who's contributed in the past or plans to
> contribute
> > in the future, please vote. If you only look at the code sometimes and
> wish
> > it more readable/understandable for you, please vote.
> >
>
> My opinions:
> 1) tabs-only, no spaces
> 2) aligned braces
> 3) always use braces even when optional
>
> I like using tabs without allowing the tabs to be converted to spaces
> because I can dynamically change the indentation depth by simply setting
> the tabstop width.  For most of the top level indentation I can widen
> the tabstops to make the code easier to scan and then, for reviewing
> deeply nested code, I can shrink the tabstops to get more text into
> view.  Of course I also code in an extra wide xterm so depth of nesting
> isn't always a problem.
>
> At least with the tabs I can go all the way down to a single space if I
> needed to or I can widen it to any large number.  The file never changes
> (the tabs are in the file already) and anyone viewing the file can see
> how many space width they want while actually coding.
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev
>