[dconf/wip/reorg: 504/523] gvdb test: Use g_string_append()



commit 17b92bd5d525db12b4e5f3b67374f34172275fd5
Author: Ryan Lortie <desrt desrt ca>
Date:   Fri Jul 6 21:39:45 2012 -0400

    gvdb test: Use g_string_append()
    
    Using g_string_append_c() causes GLib headers to appear in the test
    coverage results (since it's an inline function).  Avoid that.
    
    It's probably possible to do this in a more clever way but this works
    for now.

 tests/gvdb.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/tests/gvdb.c b/tests/gvdb.c
index 476f8b8..5c23701 100644
--- a/tests/gvdb.c
+++ b/tests/gvdb.c
@@ -195,7 +195,7 @@ walk_open (const gchar *name,
 {
   GString *log = user_data;
 
-  g_string_append_c (log, '\'');
+  g_string_append (log, "'");
   g_string_append_len (log, name, name_len);
   g_string_append_printf (log, "\'(%zd): {", name_len);
 
@@ -221,7 +221,7 @@ walk_value (const gchar *name,
 
   printed = g_variant_print (value, FALSE);
 
-  g_string_append_c (log, '\'');
+  g_string_append (log, "'");
   g_string_append_len (log, name, name_len);
   g_string_append_printf (log, "\'(%zd): %s", name_len, printed);
   g_free (printed);



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]