From 456f4a58913d851091b14552a4bdfd77f154948f Mon Sep 17 00:00:00 2001 From: Moonchild Date: Thu, 6 Feb 2020 14:50:58 +0100 Subject: Update UXP Coding Style.md Be more explicit about paranthesis spacing --- docs/UXP Coding Style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/UXP Coding Style.md') diff --git a/docs/UXP Coding Style.md b/docs/UXP Coding Style.md index 1a9568c54..75cbc8051 100644 --- a/docs/UXP Coding Style.md +++ b/docs/UXP Coding Style.md @@ -11,7 +11,7 @@ Our own managed and maintained code should adhere to this guide where possible o ## General formatting rules The following formatting rules apply to all code: - Always use spaces for indentation, never use tabs! -- Put a space between a keyword and parenthesis, e.g. `if (`. +- Put a space between a keyword and parenthesis, e.g. `if (`. Do _not_ put a space between a function/type-assignment name and its parenthesis, e.g. `function(somevar)` or `int32_t(somevar)`. - Put a space between variables and operators, e.g. `a == b`. - Put a space after a comma or semicolon in variable lists, e.g. `function(a, b, c)` or `for (i = 1; i < 10; i++)`. - Indentation of scopes is 2 spaces. -- cgit v1.2.3