More doc fixups

This commit is contained in:
Matthias Clasen 2010-03-26 10:19:57 -04:00
parent 81e2aa941b
commit 78b764f325

View File

@ -104,7 +104,7 @@ void g_io_module_unload (GIOModule *module);
* This method will not be called in normal use, however it may be
* called when probing existing modules and recording which extension
* points that this modle is used for. This means we won't have to
* load and initialze this module unless its needed
* load and initialze this module unless its needed.
*
* If this function is not implemented by the module the module will
* always be loaded, initialized and then unloaded on application startup
@ -113,16 +113,20 @@ void g_io_module_unload (GIOModule *module);
* Note that a module need not actually implement all the extension points
* that g_io_module_query returns, since the exact list of extension may
* depend on runtime issues. However all extension points actually implemented
* must be returned by g_io_module_query (if defined).
* must be returned by g_io_module_query() (if defined).
*
* When installing a module that implements g_io_module_query you must
* run gio-querymodules in order to build the cache files required for
* lazy loading.
*
* Returns: A %NULL-terminated array of strings, listing the supported
* extension points of the module. The array must be suitable for
* freeing with g_strfreev().
*
* Since: 2.24
**/
char **g_io_module_query (void);
G_END_DECLS
#endif /* __G_IO_MODULE_H__ */
#endiy /* __G_IO_MODULE_H__ */