Mercurial > hg
view mcabber/CodingStyle.txt @ 1731:4fbfae993c24
Improve login process
The roster and private storage elements are requested before broadcasting
our presence, because we want the roster before we receive our contacts
presence notifications.
This is more efficients, and also solves an issue with entity capabilities
(as we do not store caps for unknown items).
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Sun, 28 Feb 2010 18:50:30 +0100 |
parents | 189ffdd944b4 |
children | ffd0e57e9563 |
line wrap: on
line source
This document describes the preferred coding style for the mcabber project. If you intend to patch and contribute to mcabber, please try to use the existing style, and read the following points. - Do not use tabs, use space characters; - Avoid trailing whitespace; - Avoid lines longer than 80 characters; - Indentation is 2 spaces (ok, maybe it isn't a good idea but it's the current style); - Put a space after non-functions statements (e.g. if, while...) - Put the opening brace last on the same line, and put the closing brace first except for functions, where the opening brace should be alone on a new line. Example: void example(void) { if (cond1) { do_a(); } else if (cond2) { do_b(); } else { do_c(); } if (error) exit(0); } - Look at existing code for rules not mentioned here. Mikael