docs: Add a note that the printf format macros might not be compatible with system... a9164f55f7db1e620d336511ea5461207b7a06b6
| commit | a9164f55f7db1e620d336511ea5461207b7a06b6 | |
| author | Christoph Reiter <reiter.christoph@gmail.com> | |
| Sat, 5 May 2018 16:19:50 +0000 (5 18:19 +0200) | ||
| committer | Christoph Reiter <creiter@src.gnome.org> | |
| Fri, 18 May 2018 16:54:33 +0000 (18 18:54 +0200) | ||
| tree | 117bfc927aea03a5d3db7349c804fc5fc607a2ef | treesnapshot (tar.gz zip) |
| parent | 41e008266dfd489f6c7906af9414cb3ff5bb660f | commitdiff |
docs: Add a note that the printf format macros might not be compatible with system printf()
The current docs implied, by using the printf name, that the macros would
be compatible with printf(), but that's not always the case.
On Windows we use gnulib if the system printf isn't good enough.
This can happen on MinGW without __USE_MINGW_ANSI_STDIO set or with MSVC
with a varrying degree of incompatibility.
https://bugzilla.gnome.org/show_bug.cgi?id=795569
The current docs implied, by using the printf name, that the macros would
be compatible with printf(), but that's not always the case.
On Windows we use gnulib if the system printf isn't good enough.
This can happen on MinGW without __USE_MINGW_ANSI_STDIO set or with MSVC
with a varrying degree of incompatibility.
https://bugzilla.gnome.org/show_bug.cgi?id=795569
| glib/docs.c | diffblobblamehistory |