Create a check that warns about using %p printf specifier #43453
Open
Description
| Bugzilla Link | 44108 |
| Version | unspecified |
| OS | Windows NT |
Extended Description
Recently I ran into some surprising behavior surrounding the use of %p in a printf call. On Windows %p with a nullptr prints zeros, but on Linux %p with a nullptr prints "(nil)". This is surprising, but conforming to the standard which states (roughly) that the result of %p is implementation dependent.
Create a check that warns about the potential non-portable output when using %p in a printf or scanf specifier.
Activity