Home
last modified time | relevance | path

Searched refs:braces (Results 1 – 7 of 7) sorted by relevance

/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst185 various other braces can be omitted, designated initializers and not can
225 braces or not. It can be either designated or bare. For maximum
228 - Do *not* enclose *designated* initializers with braces. This is
229 required by C++20 and above which perceive such braces as mixing bare
232 - Do enclose *bare* expressions with braces. This is required by C.
234 and variations, so it may need such braces to disambiguate? Note C
235 does allow omitting most braces in initializer expressions - but not
241 braces which conflicts with this recommendation. This can be solved
/Zephyr-latest/doc/contribute/style/
Dcode.rst22 * Add braces to every ``if``, ``else``, ``do``, ``while``, ``for`` and
/Zephyr-latest/cmake/sca/eclair/ECL/
Dadopted_deviations.ecl38 …ct_lookup\", that is automatically generated, uses single-statement bodies not enclosed in braces."
/Zephyr-latest/cmake/compiler/arcmwdt/
Dcompiler_flags.cmake95 -Wno-missing-braces
/Zephyr-latest/doc/contribute/coding_guidelines/
Dindex.rst421 - The initializer for an aggregate or union shall be enclosed in braces
657 …- `EXP19-C <https://wiki.sei.cmu.edu/confluence/display/c/EXP19-C.+Use+braces+for+the+body+of+an+…
/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst379 In case you want to indicate a "variable" file path, you may use curly braces to enclose the
/Zephyr-latest/doc/releases/
Drelease-notes-2.4.rst1280 * :github:`26954` - devicetree: warning: braces around scalar initializer