[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen staging] CODING_STYLE: Custom type names must be snake-cased by word
commit eea7d98d1c653f35b40f5fd4d38a19ae8e21e8bd Author: Alejandro Vallejo <agarciav@xxxxxxx> AuthorDate: Tue Jun 24 14:54:34 2025 +0200 Commit: Jan Beulich <jbeulich@xxxxxxxx> CommitDate: Tue Jun 24 14:54:34 2025 +0200 CODING_STYLE: Custom type names must be snake-cased by word There's the unwritten convention of splitting type names using underscores. Add such convention to the CODINNG_STYLE to make it common and less unwritten. Signed-off-by: Alejandro Vallejo <agarciav@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> --- CODING_STYLE | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CODING_STYLE b/CODING_STYLE index 5644f1697f..7bf3848444 100644 --- a/CODING_STYLE +++ b/CODING_STYLE @@ -113,6 +113,12 @@ Braces should be omitted for blocks with a single statement. e.g., if ( condition ) single_statement(); +Identifiers +----------- + +When giving names to identifiers (variables, functions, constants...), separate +words using underscores (for example, use "my_foo" instead of "myfoo"). + Types ----- -- generated by git-patchbot for /home/xen/git/xen.git#staging
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |