Because you want to test if you have cracked Microsoft's piracy protection?

Spaces look great in that everything is layed out just the way the originator intended. The trouble is when you have to maintain a multitude of files that you didn't originally create and they all use a different number of spaces for indenting. You don't want to have to switch your editor's tabs/spaces. Tabs were invented for a reason. They abstractly represent an indentation without forcing a certain appearance on the viewer. Like HTML, beauty is in the eye of the beholder, not the creator. If someone wants to read their news in 16-pt Times Roman Font with double line spacing, they should be able to. Just the same, if someone wants to read your code in a manner that they are more accustomed to and is easier on their eyes, they should have a right. The chief complaint everyone has with tabs is that people mix tabs with spaces to line things up in their editor without realizing that it won't line up in someone else's. This is the true villain here. Whichever you choose, don't mix them up. I personally choose to line up my comments at a certain tab stop, though as there might still be conflicts when text runs past this point, I often don't line up my comments. I put them precisely two spaces after the code. However, on multi-line function headers, I do line up all the parameters on a common tab stop. E.g. void MyFunc1(int param1, int param2, int param3); void MyFunc2( int param1, int param2, int param3); void MyFunc3(int param1, int param2, int param3); Ironically, I had to use spaces to simulate tabs here. :laugh: The bottom line is that consistency is everything. If you use spaces, don't use tabs. If you use tabs, be careful with your spaces. After all, if it's not consistent, how can you call it a style?