Change Details

**Current situation** Currently, our code base largely follow two rules for code style as long as whitespaces are involved: * K&R/1BTS, including for method declarations * 4 spaces for indent Python code follows PEP-8 (decision taken at the start of Tasacora), PHP code follows PSR-1, but not all PSR-2 (which isn't a K&R style). **Proposal to adopt llvm style as C code style** So, to be coherent, I suggest we use use llvm as code style, so we can get a K&R/1TBS style. It also introduces sensible pointer/reference symbols positions helping to avoid mistakes like `char* foo, bar`: the llvm style will rewrite that as `char *foo, bar`, allowing immediately to see something is wrong. The only restriction I would bring is the spacing, they indent as 2 spaces, we'll use 4 to be coherent with PEP-8 and the rest of the languages. **Tools to reformat automatically and enforce this style** Furthermore, clang provides a good linter, [[ http://clang.llvm.org/docs/ClangFormat.html | clang-format ]], not only to detect style issues, but also able to reformat the code with this style. We can integrate it with Arcanist, and so avoid to waste time in reviews to point style issues, as it would have already be `arc lint` (called by `arc diff`). Currently, it requires to install a plug-in for Arcanist, but linter author and Phabricator project both agree to directly integrate it to Arcanist. This also helps to gain time. For example, it allows to correctly transform a long line into a nicely aligned block, cut after 80 characters: ``` static int mq_command(ClientData clientData, Tcl_Interp *tclInterpreter, int argc, char **argv) { ... } ``` Here a configuration file for `clang-format` with the style I suggest: {F14479}