luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-07-30 22:03:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

documentation fixes

Browse Source 
Fixes for gtk-doc warnings.

http://bugzilla.gnome.org/show_bug.cgi?id=66469

https://bugzilla.gnome.org/show_bug.cgi?id=664699
This commit is contained in:
Stef Walter
2011-12-13 23:00:16 -05:00
committed by Matthias Clasen
parent b0c3997fdd
commit 7e92997539
28 changed files with 169 additions and 127 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
glib/gtestutils.c
View File

@@ -260,7 +260,7 @@
* an error message is logged and the application is terminated.
*
* The macro can be turned off in final releases of code by defining
* #G_DISABLE_ASSERT when compiling the application.
* <envar>G_DISABLE_ASSERT</envar> when compiling the application.
*/
/**
@@ -271,7 +271,7 @@
* application is terminated.
*
* The macro can be turned off in final releases of code by defining
* #G_DISABLE_ASSERT when compiling the application.
* <envar>G_DISABLE_ASSERT</envar> when compiling the application.
*/
/**
@@ -1281,10 +1281,10 @@ g_test_run (void)
* Create a new #GTestCase, named @test_name, this API is fairly
* low level, calling g_test_add() or g_test_add_func() is preferable.
* When this test is executed, a fixture structure of size @data_size
* will be allocated and filled with 0s. Then data_setup() is called
* will be allocated and filled with 0s. Then @data_setup is called
* to initialize the fixture. After fixture setup, the actual test
* function data_test() is called. Once the test run completed, the
* fixture structure is torn down by calling data_teardown() and
* function @data_test is called. Once the test run completed, the
* fixture structure is torn down by calling @data_teardown and
* after that the memory is released.
*
* Splitting up a test run into fixture setup, test function and
@@ -1557,7 +1557,7 @@ g_test_queue_free (gpointer gfree_pointer)
* @destroy_func: Destroy callback for teardown phase.
* @destroy_data: Destroy callback data.
*
* This function enqueus a callback @destroy_func() to be executed
* This function enqueus a callback @destroy_func to be executed
* during the next test case teardown phase. This is most useful
* to auto destruct allocted test resources at the end of a test run.
* Resources are released in reverse queue order, that means enqueueing