[Top][All Lists]

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

[bug #52463] anything that talks to standard error should identify itsel

From: G. Branden Robinson
Subject: [bug #52463] anything that talks to standard error should identify itself
Date: Mon, 6 Jun 2022 22:39:47 -0400 (EDT)

Follow-up Comment #4, bug #52463 (project groff):

2022-06-04  G. Branden Robinson <g.branden.robinson@gmail.com>

        * src/devices/gropdf/gropdf.pl: Revise diagnostic message
        (top level): Add new scalar `progname` to house executable name.
        (Msg): Output messages in format recommended by GNU Coding
        Standards manual.  Identify who's talking (Savannah #52463).
        Rename `lev` scalar to `fatal` since it is used only as a
        Boolean for immediately exiting with failure status.  Report
        diagnostic severity as part of message.
        (Warn, Die): Add new subroutines through which all diagnostics
        are now emitted.
        (top level): Migrate a use of Perl `die` builtin to our `Die`.
        (top level, ToPoints, LoadDownload, LoadDesc, do_x, GetPoints,
        LoadSWF, LoadPDF, LoadStream, BuildStream, ParsePDFHash,
        LoadFont, GetType1, GetChunk, RemapChr, do_N): Migrate `Msg(0,
        ...)` calls to `Warn` and `Msg(1, ...)` to `Die`.  Begin
        messages in lowercase (GNU Coding Standards).  Recast a few
        messages for clarity.

        Continues the long process of fixing Savannah #52463.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]