Re: mdocml: Implement a simple, consistent user interface for error

[Kristaps Dzonsons <kristaps@bsd.lv>]

> Log Message:
> -----------
> Implement a simple, consistent user interface for error handling.
> We now have sufficient practical experience to know what we want,
> so this is intended to be final:
> - provide -Wlevel (warning, error or fatal) to select what you care about
> - provide -Wstop to stop after parsing a file with warnings you care about
> - provide consistent exit status codes for those warnings you care about
> - fully document what warnings, errors and fatal errors mean
> - remove all other cruft from the user interface, less is more:
> - remove all -f knobs along with the whole -f option
> - remove the old -Werror because calling warnings "fatal" is silly
> - always finish parsing each file, unless fatal errors prevent that
> This commit also includes a couple of related simplifications behind
> the scenes regarding error handling.
> Feedback and OK  kristaps@;  Joerg Sonnenberger (NetBSD) and
> Sascha Wildner (DragonFly BSD) agree with the general direction.

Ingo, a small thing I don't have the time to ferret out:

.Dd $Mdocdate$
.Dt FOO 1
.Os
.Sh NAME
.Nm foo
.Nd bar
.Sh DESCRIPTION
\(
.Bk

Different results:

% ./mandoc -Wall foo.1 ; echo $?
foo.1:8:1: WARNING: bad escape sequence
foo.1:9:2: FATAL: scope broken, syntax violated
4
% ./mandoc -Wall,stop foo.1 ; echo $?
foo.1:8:1: WARNING: bad escape sequence
2

Am I just being dumb here?  Shouldn't the second one roll over the 
WARNING into the FATAL as well?

Kristaps
--
 To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv