After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741049 - gmessages: clarify what log levels are for
gmessages: clarify what log levels are for
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-12-02 23:49 UTC by Allison Karlitskaya (desrt)
Modified: 2018-04-23 12:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gmessages: clarify what log levels are for (4.25 KB, patch)
2014-12-02 23:49 UTC, Allison Karlitskaya (desrt)
committed Details | Review

Description Allison Karlitskaya (desrt) 2014-12-02 23:49:01 UTC
For a long time we've had it as 'common knowledge' that criticals are
for programmer errors and warnings are for external errors, but we've
never documented that.  Do so.
Comment 1 Allison Karlitskaya (desrt) 2014-12-02 23:49:27 UTC
Created attachment 292031 [details] [review]
gmessages: clarify what log levels are for

For a long time we've had it as 'common knowledge' that criticals are
for programmer errors and warnings are for external errors, but we've
never documented that.  Do so.
Comment 2 Philip Withnall 2015-03-03 18:57:46 UTC
Review of attachment 292031 [details] [review]:

::: docs/reference/glib/running.xml
@@ +124,3 @@
         <listitem><para>Causes GLib to abort the program at the first call
+           to g_warning() or g_critical().  Use of this flag is not
+           recommended.</para>

‘except when debugging’?

::: glib/gmessages.c
@@ +213,3 @@
+ * Critical errors can be fatal (ie: result in termination of the
+ * program) if the `G_DEBUG` environment variable is set accordingly.
+ * See [Running GLib Applications](glib-running.html).  You can also use

Is that xref correct? docs/reference/glib/running.html gives the <refentry id> as simply ’glib-running’.
Comment 3 Philip Withnall 2018-04-23 12:02:24 UTC
(In reply to Philip Withnall from comment #2)
> Review of attachment 292031 [details] [review] [review]:
> 
> ::: docs/reference/glib/running.xml
> @@ +124,3 @@
>          <listitem><para>Causes GLib to abort the program at the first call
> +           to g_warning() or g_critical().  Use of this flag is not
> +           recommended.</para>
> 
> ‘except when debugging’?

I’ve made this change locally.

> ::: glib/gmessages.c
> @@ +213,3 @@
> + * Critical errors can be fatal (ie: result in termination of the
> + * program) if the `G_DEBUG` environment variable is set accordingly.
> + * See [Running GLib Applications](glib-running.html).  You can also use
> 
> Is that xref correct? docs/reference/glib/running.html gives the <refentry
> id> as simply ’glib-running’.

It is the correct xref. Not changing it.
Comment 4 Philip Withnall 2018-04-23 12:03:59 UTC
Comment on attachment 292031 [details] [review]
gmessages: clarify what log levels are for

Rebased on master, rearranged a bit to fit with the current docs, fixed my first review comment from above, ignored the second, and pushed.

Attachment 292031 [details] pushed as ad3b2f2 - gmessages: clarify what log levels are for