1. 09 Jul, 2019 1 commit
  2. 27 Jun, 2019 2 commits
  3. 26 Jun, 2019 2 commits
  4. 28 Jan, 2019 2 commits
    • Emmanuel Fleury's avatar
      Fixing signedness in g_ptr_array_insert():glib/garray.c · a4191465
      Emmanuel Fleury authored
      glib/garray.c: In function ‘g_ptr_array_insert’:
      glib/garray.c:1522:14: error: comparison of integer expressions of different signedness: ‘gint’ {aka ‘int’} and ‘guint’ {aka ‘unsigned int’} [-Werror=sign-compare]
         if (index_ < rarray->len)
                    ^
      a4191465
    • Emmanuel Fleury's avatar
      Fixing signedness in g_ptr_array_maybe_expand():garray.c · 5ca8c2fa
      Emmanuel Fleury authored
      ../glib.git/glib/garray.c: In function ‘g_ptr_array_maybe_expand’:
      ../glib.git/glib/garray.c:1172:43: error: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘gint’ {aka ‘int’} [-Werror=sign-compare]
         if G_UNLIKELY ((G_MAXUINT - array->len) < len)
      5ca8c2fa
  5. 24 Sep, 2018 2 commits
    • Debarshi Ray's avatar
      docs: Simplify the text for g_array_free · 0a8f3698
      Debarshi Ray authored
      The text about deallocation of GArrays with elements containing
      dynamically-allocated memory was confusing. It initially mentioned
      clear_func, but later said elements with dynamically allocated memory
      "should be freed separately".
      
      Clarify this by using the same structure as g_ptr_array_free —
      highlight the need to set a clear_func by consolidating the text about
      it in a separate paragraph.
      
      GNOME/glib!348
      0a8f3698
    • Debarshi Ray's avatar
      docs: Use the correct terminology for g_array_free · 30ccd6f0
      Debarshi Ray authored
      GArray uses the term clear_func (eg., g_array_set_clear_func), while
      element_free_func comes from GPtrArray.
      
      GNOME/glib!348
      30ccd6f0
  6. 24 Jul, 2018 1 commit
    • Christian Hergert's avatar
      garray: add overflow checks before expanding array · 0c7dc758
      Christian Hergert authored
      We should bail when we detect that adding a number of items to an array
      would cause it to overflow. Since we can't change to using gsize for ABI
      reasons we should protect the integrity of the process even if that means
      crashing.
      0c7dc758
  7. 10 Jul, 2018 1 commit
  8. 11 Jun, 2018 1 commit
  9. 04 Jun, 2018 3 commits
  10. 09 May, 2018 3 commits
  11. 20 Apr, 2018 1 commit
  12. 23 Feb, 2018 1 commit
  13. 16 Nov, 2017 1 commit
  14. 22 Aug, 2017 1 commit
  15. 24 May, 2017 1 commit
    • Sébastien Wilmet's avatar
      glib/: LGPLv2+ -> LGPLv2.1+ · f9faac76
      Sébastien Wilmet authored
      All glib/*.{c,h} files have been processed, as well as gtester-report.
      
      12 of those files are not licensed under LGPL:
      
      	gbsearcharray.h
      	gconstructor.h
      	glibintl.h
      	gmirroringtable.h
      	gscripttable.h
      	gtranslit-data.h
      	gunibreak.h
      	gunichartables.h
      	gunicomp.h
      	gunidecomp.h
      	valgrind.h
      	win_iconv.c
      
      Some of them are generated files, some are licensed under a BSD-style
      license and win_iconv.c is in the public domain.
      
      Sub-directories inside glib/:
      
      	deprecated/: processed in a previous commit
      	glib-mirroring-tab/: already LGPLv2.1+
      	gnulib/: not modified, the code is copied from gnulib
      	libcharset/: a copy
      	pcre/: a copy
      	tests/: processed in a previous commit
      
      https://bugzilla.gnome.org/show_bug.cgi?id=776504
      f9faac76
  16. 02 May, 2017 1 commit
  17. 02 Dec, 2016 1 commit
  18. 22 Nov, 2016 1 commit
  19. 09 Mar, 2016 1 commit
  20. 07 Nov, 2015 1 commit
    • Philip Withnall's avatar
      glib: Add missing (nullable) and (optional) annotations · 25a7c817
      Philip Withnall authored
      Add various (nullable) and (optional) annotations which were missing
      from a variety of functions. Also port a couple of existing (allow-none)
      annotations in the same files to use (nullable) and (optional) as
      appropriate instead.
      
      Secondly, add various (not nullable) annotations as needed by the new
      default in gobject-introspection of marking gpointers as (nullable). See
      https://bugzilla.gnome.org/show_bug.cgi?id=729660.
      
      This includes adding some stub documentation comments for the
      assertion macro error functions, which weren’t previously documented.
      The new comments are purely to allow for annotations, and hence are
      marked as (skip) to prevent the symbols appearing in the GIR file.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=719966
      25a7c817
  21. 08 Oct, 2014 1 commit
  22. 13 Sep, 2014 1 commit
    • Sébastien Wilmet's avatar
      docs: various small fixes · 25990eb2
      Sébastien Wilmet authored
      For the GPtrArray example, several variables declared on the same line
      is harder to read and to work with (to move, remove or comment a single
      variable declaration).
      25990eb2
  23. 15 Feb, 2014 1 commit
    • Matthias Clasen's avatar
      docs: let go of &ast; · bc6ee788
      Matthias Clasen authored
      Since we are no longer using sgml mode, using /&ast; &ast;/ to
      escape block comments inside examples does not work anymore.
      Switch to using line comments with //
      bc6ee788
  24. 02 Feb, 2014 3 commits
  25. 01 Feb, 2014 3 commits
  26. 31 Jan, 2014 3 commits