Files
glib/tests
Emmanuele Bassi 5e516be777 Use C99 integer types where appropriate
GLib depends on various parts of a valid C99 toolchain, so it's time to
use C99 integer types wherever possible, instead of doing configure-time
discovery like it's 1997.

So:

  gint8   → int8_t      guint8   → uint8_t
  gint16  → int16_t     guint16  → uint16_t
  gint32  → int32_t     guint32  → uint32_t
  gint64  → int64_t     guint64  → uint64_t
                        gsize    → size_t
  gintptr → intptr_t    guintptr → uintptr_t

There are some side effects on switching to C99:

 - the G_*_MODIFIER macros do not really make any more sense, and should
 be deprecated and replaced by an empty string
 - the G_*_FORMAT macros are marked for use with both printf() and
 scanf(), except that's not really true at all; C99 defines format
 macros for print() and scanf() separately, and GLib should do the
 same. The old macros should be deprecated, but if we want to be evil
 about it, we could alias them with the PRINTF_FORMAT, as it's likely
 their more dominant use

In general, there shouldn't be any ABI changes, unless the toolchain in
use is not conformant to C99.

Closes #1484
2019-12-19 16:30:12 +00:00
..
2005-10-05 17:37:46 +00:00
2017-05-29 19:53:35 +02:00
2018-09-21 08:45:54 -04:00
2017-05-29 19:53:35 +02:00
2017-05-29 19:53:35 +02:00
2017-05-29 19:53:35 +02:00
2017-05-29 19:53:35 +02:00
2012-11-15 14:19:06 -05:00
2017-05-29 19:53:35 +02:00
2017-05-29 19:53:35 +02:00
2017-05-29 19:53:35 +02:00
2011-05-01 17:10:04 -04:00
2017-05-29 19:53:35 +02:00
2019-10-09 16:39:31 +02:00
2013-11-10 22:44:12 +01:00