Tabs vs Spaces (yes, again!)

PIG DISGUSTING

{
    int a    = 3;
    int ab    = 4;
    // ...
}


{
   int a  = 3;
   int ab = 4;
}

BEAUTIFUL AND NICE

{
    int a  = 3;
    int ab = 4;
}

Style 1 (all tabs) will look fucked up vertical alignment with different tab widths. Style 2 (all spaces) will look weird to those used to different tab widths. Style 3 (tabs to indent, spaces to align), on the other hand, is made of epic win because it allows one to change the tab width without losing the nice vertical alignment, and those who really like all spaces can easily have their editor auto-convert tabs to spaces.

Style 3 > Style 2 > Style 1. If you use Style 1, you're an asshole.

>>25
I was just thinking about something like that. Then editors could provide type-checking! But your idea is a tad too verbose.


<argument name="argv">
  <type pointers="2">char</type>
</argument>
 ...
<return>
  <literal value="0">
    <type>int</type>
  </literal>
</return>

Hey, /prog/, maybe we should get to writing a standard for storing C code as XML. We'd have to write a plugin for some editor too (probably emacs, cause then we'd just need to distribute a .el file.)