Coding Style about opmon-archive

[milkyroute]

Ok I will anwser using the same model as you :

• Tab vs spaces: SmartTabs (I think it is a good idea)
• Spaces between class name and following curly brace: Yes (That is what I want to do since the beginning but I forget to add the space each time a add a curly brace)
• Spaces between keyword (if, for) and following parenthesis: No
• Spaces before curly brace on control flow statements (if, for, etc.): Yes
• Spaces before the curly brace opening the function: Yes
• Using _ prefix for private member variables: The programmer chooses. I won't use it myself, but if somebody is used to do this, I don't have any problems with it. Do what you want.
• Should we indent case in switch statements ? No
• Should we indent public, private and protected ? No
• Should we indent the namespaces ? Yes (It's more organized like that, and the code seems more "ventilated")