1. 31 Jan, 2014 4 commits
  2. 23 Jan, 2014 1 commit
  3. 20 Jan, 2014 1 commit
  4. 31 Dec, 2013 4 commits
  5. 17 Dec, 2013 2 commits
  6. 15 Dec, 2013 1 commit
  7. 04 Dec, 2013 1 commit
  8. 03 Dec, 2013 2 commits
  9. 29 Nov, 2013 1 commit
  10. 27 Nov, 2013 1 commit
    • Allison Karlitskaya's avatar
      tests: move /param/implement to -m slow · 30e1ab32
      Allison Karlitskaya authored
      Take this test out of 'make check'.  It's causing problems for a lot of people
      due to fact that it's essentially a forkbomb.  It's causing failures for Debian
      on ARM and it's DoSing coredumps to system crash collectors.
      
      The conditional only covers registration of the master, not the
      subprocess parts.  This is because g_test_slow() always return FALSE in
      the subprocesses, so they would fail to run if we didn't register them
      unconditionally.
      30e1ab32
  11. 24 Nov, 2013 1 commit
  12. 23 Nov, 2013 3 commits
  13. 20 Nov, 2013 2 commits
    • Dan Winship's avatar
      Replace #ifdef HAVE_UNISTD_H checks with #ifdef G_OS_UNIX · 158dde05
      Dan Winship authored
      In Windows development environments that have it, <unistd.h> is mostly
      just a wrapper around several other native headers (in particular,
      <io.h>, which contains read(), close(), etc, and <process.h>, which
      contains getpid()). But given that some Windows dev environments don't
      have <unistd.h>, everything that uses those functions on Windows
      already needed to include the correct Windows header as well, and so
      there is never any point to including <unistd.h> on Windows.
      
      Also, remove some <unistd.h> includes (and a few others) that were
      unnecessary even on unix.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=710519
      158dde05
    • Dan Winship's avatar
      Require C90 compliance · 6e4a7fca
      Dan Winship authored
      Assume all supported platforms implement C90, and therefore they
      (correctly) implement atexit(), memmove(), setlocale(), strerror(),
      and vprintf(), and have <float.h> and <limits.h>.
      
      (Also remove the configure check testing that "do ... while (0)" works
      correctly; the non-do/while-based version of G_STMT_START and
      G_STMT_END was removed years ago, but the check remained. Also, remove
      some checks that configure.ac claimed were needed for libcharset, but
      aren't actually used.)
      
      Note that removing the g_memmove() function is not an ABI break even
      on systems where g_memmove() was previously not a macro, because it
      was never marked GLIB_AVAILABLE_IN_ALL or listed in glib.symbols, so
      it would have been glib-internal since 2004.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=710519
      6e4a7fca
  14. 15 Nov, 2013 1 commit
  15. 11 Nov, 2013 4 commits
  16. 06 Nov, 2013 2 commits
  17. 29 Oct, 2013 1 commit
  18. 22 Oct, 2013 2 commits
  19. 06 Oct, 2013 1 commit
    • Dan Winship's avatar
      Fix overloading of "source" and "target" terminology in GBinding · 8e17040c
      Dan Winship authored
      GBindingTransformFunc called its arguments "source_value" and
      "target_value", but in the transform_from function of a bidirectional
      binding, "source_value" comes from the target object, and
      "target_value" comes from the source object, which quickly gets
      confusing if you need to use g_binding_get_source(), etc, in the
      function.
      
      Of course developers can call their transform function arguments
      whatever they want, but many will copy from the headers/docs to start
      out, so use less confusing names here ("from_value" and "to_value").
      
      Also, fix the documentation to describe the bidirectional case
      correctly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=709440
      8e17040c
  20. 02 Oct, 2013 1 commit
  21. 19 Sep, 2013 1 commit
  22. 02 Sep, 2013 2 commits
  23. 27 Aug, 2013 1 commit
    • Dan Winship's avatar
      gtype: fix a no-op assertion · 34e1a537
      Dan Winship authored
      g_type_class_add_private() was doing
      
          g_assert (node->data->instance.private_size <= 0xffff);
      
      but that field is a guint16, so the check was a no-op. (Noticed by
      clang, but not gcc for some reason.) Fix it to do the math in a gssize
      variable and do the bounds checking there before updating the struct
      field.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=706888
      34e1a537