projects / platform / upstream / glib.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 299ca6d) | patch
gtestutils: make the new assert messages more detailed
authorDan Winship <danw@gnome.org>
Fri, 14 Feb 2014 21:12:50 +0000 (16:12 -0500)
committerDan Winship <danw@gnome.org>
Mon, 17 Feb 2014 16:33:37 +0000 (11:33 -0500)
commit5a4478664be8bc6523f6452bfd63340718be2aa5
treec87af78e6be7cc66ce6997ed0abdaad03358c659tree | snapshot
parent299ca6dc1e54797e6fc5264c7b19b08bd726ca83commit | diff
gtestutils: make the new assert messages more detailed

g_assert_true(), g_assert_false(), g_assert_null(), and
g_assert_nonnull() simply printed out the expression they were
checking, without any further explanation of what went wrong. (In
particular, "g_assert_true(x)" and "g_assert_false(x)" would both
print the same thing on failure.) Add a little bit more context.

https://bugzilla.gnome.org/show_bug.cgi?id=724385
glib/gtestutils.h diff | blob | history
Domain: System / Base;