fix(print): Fix format specifiers #12164
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
This pull request standardizes the usage of format specifiers in
Serial.printfcalls across multiple example files, replacing%dand%uwith%zu(forsize_tvalues) and%lu(forunsigned longvalues). This improves type safety and ensures correct output formatting, especially on platforms wheresize_tand related types may differ in size fromintorunsigned int.Serial output formatting improvements:
%dand%uwith%zuinSerial.printfstatements for variables of typesize_tin UDP, Bluetooth, BLE, and Serial examples, ensuring proper formatting for buffer sizes, data lengths, and counts. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23]%ldto%luinSerial.printfforunsigned longvariables, such as delay times, to match the variable type in deep sleep and progress reporting examples. [1] [2]These changes help prevent formatting errors and potential undefined behavior, making the code more robust and portable across platforms.