glib/gmodule
Christian Hergert 18a33f72db introspection: use (nullable) or (optional) instead of (allow-none)
If we have an input parameter (or return value) we need to use (nullable).
However, if it is an (inout) or (out) parameter, (optional) is sufficient.

It looks like (nullable) could be used for everything according to the
Annotation documentation, but (optional) is more specific.
2016-11-22 14:14:37 -08:00
..
.gitignore improve gitignore 2010-01-28 22:43:51 -05:00
AUTHORS initial import of gmodule. 1998-08-09 08:32:18 +00:00
ChangeLog Update README files to refer to git 2009-03-31 19:39:16 -04:00
COPYING initial import of gmodule. 1998-08-09 08:32:18 +00:00
gmodule-ar.c Updated FSF's address 2014-01-31 14:31:55 +01:00
gmodule-dl.c Updated FSF's address 2014-01-31 14:31:55 +01:00
gmodule-dyld.c Updated FSF's address 2014-01-31 14:31:55 +01:00
gmodule-win32.c Updated FSF's address 2014-01-31 14:31:55 +01:00
gmodule.c introspection: use (nullable) or (optional) instead of (allow-none) 2016-11-22 14:14:37 -08:00
gmodule.h Updated FSF's address 2014-01-31 14:31:55 +01:00
gmodule.rc.in Update the year in the *.rc.in files 2011-06-07 08:55:31 +08:00
gmoduleconf.h.in Updated FSF's address 2014-01-31 14:31:55 +01:00
gmoduleconf.h.win32 Updated FSF's address 2014-01-31 14:31:55 +01:00
Makefile.am win32: fixup lib.exe invocation 2014-02-15 16:55:25 -05:00
makefile.msc.in adapt to gmodule.symbols usage 2008-08-01 14:17:43 +00:00