Lines Matching refs:spaces

47 …eviation in the phrase begins with a capital letter, and with no intervening spaces or punctuation.
387 ### Rule 2.2 Use spaces to indent and indent four spaces at a time.
389 Only spaces can be used for indentation. Four spaces are indented each time. Do not use the Tab cha…
391 …omatic conversion of a Tab input to fours spaces. Configure your code editor to support indentatio…
445 …ArgType paramName3, ArgType paramName4, ArgType paramName5) // Good: 4 spaces are used for ind…
451 …ArgType paramName1, ArgType paramName2, ArgType paramName3) // Good: 4 spaces are used for indenta…
475 …paramName3, paramName4, paramName5); // Good: 4 spaces are used for indentation.
478 paramName1, paramName2, paramName3); // 4 spaces are used for indentation.
610 After an expression is wrapped, ensure that the lines are properly aligned or indented by 4 spaces.…
614 longVariableName4 + longVariableName5 + longVariableName6; // OK: indented with 4 spaces
661 For the struct or array initialization, use 4 spaces for indentation if a line break is made.
768 Horizontal spaces should be used to highlight keywords and important information. Do not add spaces
770 - Add spaces after keywords such as `if`, `switch`, `case`, `do`, `while`, and `for`.
771 - Do not add spaces after the left parenthesis or before the right parenthesis.
775 - Add spaces before and after the colon of bit field description.
776 - Do not add spaces between ++/-- and variables.
777 - Do not add spaces before and after the struct member operator (. ->).
778 - Adding or not adding spaces inside the brace must be consistent.
779 …Do not add spaces before commas, semicolons, or colons (excluding the colon in the ternary operato…
780 - Do not add spaces between the parentheses of the function parameter list and the function name.
781 - Do not add spaces between the parenthesis of the type cast and the object being converted.
782 - Do not add spaces between the square bracket of the array and the array name.
785 For spaces inside the braces, the following **recommendations** are available:
787 - It is recommended that spaces be added after the left brace and before the right brace.
788 - For an empty constant or a constant with a single identifier or a single word, spaces are not req…
789 …' is a bad example, since it is not a consecutively nested scene and the spaces inside the outermo…
794 int i = 0; // Good: When the variable is initialized, there should be spaces befor…
795 int buf[BUF_SIZE] = {0}; // Good: For array initialization, spaces in curly braces are optional.
857 Note: The current IDE and code editor can be set to delete spaces at the end of a line. Configure y…
1057 Leave at least one space between the code and the comment on the right. No more than four spaces ar…
1060 You can use the extended Tab key to indent 1-4 spaces.
1071 After the alignment, ensure that the comment is 1–4 spaces separated from the closest code line on …
1078 #define ANOTHER_CONST 200 /* Leave spaces after code to align comments vertically. */