> On Jul 28, 2017, at 2:58 PM, Vasco Alexandre da Silva Costa
> <vasco.co...@gmail.com> wrote:
>
> On Fri, Jul 28, 2017 at 10:46 PM, Marco Domingues <marcodomingue...@gmail.com
> <mailto:marcodomingue...@gmail.com>> wrote:
> I’m using Visual Studio Code, which wasn’t configured properly! Well after
> configuring it I could see how bad I was indenting the code, so I would like
> to apology for that!
>
> I’ve uploaded the patch with the regiontable optimization, and from now on
> the patches should be indented accordingly to the code standards! Sorry again!
>
> It had to be Microsoft... No UNIX person would use 4 space tabs. :-)
Au contraire. :)
It was simply a compromise decision prior to going open source, a balance of
compression (tabs) with fixed presentation (spaces), quite effectively avoiding
bike-shed debates. When a codebase survives authors (by decades), it’s more
important that the code be consistent.
Of course siding with both camps meant the downsides of both too and, more
unforeseen but obvious in hindsight, would be a common stumbling point for new
contributors.
Since then, there’s been consensus that switching to tabs would be fine.
That'll should happen after astyle enforcement gets turned on (so style errors
result in compile failures), which is real-soon-now.
Cheers!
Sean
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
