Note also that the guideline specifically states that tabs must be 8 spaces, which eradicates the "flexibility" that tabs would give you anyway. So here, spaces are used for indentation past the first level. So this is saying to use tabs between void and usage, again alignment and not indentation. Prototypes may have an extra space after a tab to enable function names to line up: static char *function(int _arg, const char *_arg2, struct foo *_arg3, This is saying to align foo and bar below using tabs: struct Try to make the structure readable by aligning the member names using either one or two tabs depending upon your judgment. Really? From scanning through the FreeBSD guidelines: I usually tend to just stick with whatever the standard is for a language if there is one.Īll 3 BSDs (not just kernels but entire operating sytems) For SQL or PL/SQL I use spaces as otherwise I end up with a mix of tabs and spaces. For Python I follow PEP 8 and use 4 spaces. I like 4 space indentation, so 2 space indentation take a little adjustment, and 8 spaces would be just annoying. Using spaces only has some advantages, but then people can't set their indention levels to whatever they want. Tabs make a lot of sense for various reasons, but when you need to line things up with things that don't fall on a tab-stop you end up using spaces in combination with tabs which is somewhat awkward (and apparently get beat down according to the picture). I mean, I have no problem conforming to whatever a project or team's standards are, but often times I am in charge of coming up with the standard or am working on my own personal project.
#Nedit replace tabs with spaces code#
If there is no code in your link, it probably doesn't belong here.