From 53b4806f0007aa2ae5829e405b50b84bdfb9734d Mon Sep 17 00:00:00 2001 From: Jakob Hasse Date: Wed, 10 May 2023 16:38:30 +0800 Subject: [PATCH] doc: clarified migration guide regarding PRIxx usage --- docs/en/migration-guides/release-5.x/5.0/gcc.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/migration-guides/release-5.x/5.0/gcc.rst b/docs/en/migration-guides/release-5.x/5.0/gcc.rst index bef17c2f44..eba08800a2 100644 --- a/docs/en/migration-guides/release-5.x/5.0/gcc.rst +++ b/docs/en/migration-guides/release-5.x/5.0/gcc.rst @@ -114,7 +114,7 @@ The types ``int32_t`` and ``uint32_t`` have been changed from the previous ``int - (unsigned) long -The change mostly affects code that formats strings using types provided by ````. Users will need to replace placeholders such as ``%i`` and ``%x`` with ``PRIi32`` and ``PRIxx`` respectively. +The change mostly affects code that formats strings using types provided by ````. When using these fixed-width types (e.g. ``uint32_t```), users will need to replace placeholders such as ``%i`` and ``%x`` with ``PRIi32`` and ``PRIx32`` respectively. Types *not* defined in ```` (e.g. ``int``) do *not* need this special formatting. In other cases, it should be noted that enums have the ``int`` type.