Mercurial > ~mikael > mcabber > hg
view mcabber/CodingStyle.txt @ 2358:b010ffcae282
Don't crash on presence from bare room JID
While handling MUC presence, check whether it was sent from the bare
room JID before assuming a non-NULL resource name. These days, some
servers send presence from the bare room JID to handle MUC avatars.
author | Holger Weiß <holger@zedat.fu-berlin.de> |
---|---|
date | Tue, 22 Oct 2019 19:59:21 +0200 |
parents | ffd0e57e9563 |
children |
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); - Defined types shall end with _t - 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