News for hackers. Stuff that matters.
Re:NASA C Style Guide [pdf] by satysin on Saturday November 19, 2016 @03:41PM (#12995510)
4 space indentation and not tabs. What would Hendricks say?!
Re:NASA C Style Guide [pdf] by bunderbunder on Saturday November 19, 2016 @05:07PM (#12995955)
Tabs really only works easily when everyone's using the same editor settings. Otherwise, it quickly devolves into a mess.

Spaces really only works easily when everyone uses an editor that can convert presses of the tab key into some number of space characters.

The only solution that works easily in all cases is to flatly refuse to collaborate with others.

Re:NASA C Style Guide [pdf] by Redoubts on Saturday November 19, 2016 @07:00PM (#12996438)
> Spaces really only works easily when everyone uses an editor that can convert presses of the tab key into some number of space characters.

Could you show me an editor that doesn't do that?

Re:NASA C Style Guide [pdf] by EliRivers on Sunday November 20, 2016 @12:01PM (#12999783)
I just finished three years in a job in which I worked on a GUI containing an editor that does not do that.
Re:NASA C Style Guide [pdf] by tscs37 on Saturday November 19, 2016 @04:32PM (#12995810)
I'd personally say 4 spaces on even indentation levels and tabs everywhere else.