Philippe Mathieu-Daudé <[email protected]> writes:
> Signed-off-by: Philippe Mathieu-Daudé <[email protected]> > --- > docs/devel/style.rst | 59 ++++++++++++++++++++++---------------------- > 1 file changed, 30 insertions(+), 29 deletions(-) > > diff --git a/docs/devel/style.rst b/docs/devel/style.rst > index e00af62e763..3e519dc6ade 100644 > --- a/docs/devel/style.rst > +++ b/docs/devel/style.rst > @@ -111,7 +111,7 @@ Variables are lower_case_with_underscores; easy to type > and read. Structured > type names are in CamelCase; harder to type but standing out. Enum type > names and function type names should also be in CamelCase. Scalar type > names are lower_case_with_underscores_ending_with_a_t, like the POSIX > -uint64_t and family. Note that this last convention contradicts POSIX > +``uint64_t`` and family. Note that this last convention contradicts POSIX > and is therefore likely to be changed. > > Variable Naming Conventions > @@ -290,57 +290,57 @@ a few useful guidelines here. > Scalars > ------- > > -If you're using "int" or "long", odds are good that there's a better type. > -If a variable is counting something, it should be declared with an > -unsigned type. > +If you're using '``int``' or '``long``', odds are good that there's a > better We seem to be switching between quoted and unquoted ``types``. Are the quotes really needed if they are also highlighted by the monospace font? Either way: Reviewed-by: Alex Bennée <[email protected]> -- Alex Bennée
