1. 23 Jan, 2019 3 commits
  2. 22 Jan, 2019 9 commits
  3. 21 Jan, 2019 8 commits
  4. 19 Jan, 2019 1 commit
  5. 18 Jan, 2019 8 commits
  6. 17 Jan, 2019 8 commits
  7. 16 Jan, 2019 1 commit
  8. 15 Jan, 2019 2 commits
    • Michael Catanzaro's avatar
      Merge branch 'mcatanzaro/g_assert_cpp' into 'master' · 193cc669
      Michael Catanzaro authored
      Add separate definitions of g_assert_[non]null() for C++
      See merge request GNOME/glib!568
    • Michael Catanzaro's avatar
      Add separate definitions of g_assert_[non]null() for C++ · 4a0ce6b4
      Michael Catanzaro authored
      In C++ we can use nullptr to ensure g_assert_[non]null() is only called
      with pointers. This will introduce build failures in tests that would
      have previously compiled, but only in C++, and only for code that
      misused these macros. Code using the macros properly will be fine.
      This change caught a couple bugs in WebKit's API tests, where I had
      accidentally used these functions improperly. E.g. this is now a build
      failure in C++:
      g_assert_null(webkit_context_menu_get_n_items(menu)); /* Oops! */
      Either I wanted to use cmpuint there, or I wanted to use
      webkit_context_menu_get_items() to receive a GList* instead.
      Another example that will no longer build in C++:
      g_assert_null(0); /* Contrived, but 0 is not a pointer! */