summaryrefslogtreecommitdiff
path: root/dviware/dvi2bitmap/doc_libdvi2bitmap/man/man3/verbosity.h.3
blob: f05b166c5996735088370901d6bddc74dc0ad7a0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
.TH "verbosity.h" 3 "Mon Jan 12 2015" "Version dvi2bitmap1.0" "dvi2bitmap" \" -*- nroff -*-
.ad l
.nh
.SH NAME
verbosity.h \- 
.SH SYNOPSIS
.br
.PP
.SS "Enumerations"

.in +1c
.ti -1c
.RI "enum \fBverbosities\fP { \fBsilent\fP, \fBquiet\fP, \fBnormal\fP, \fBdebug\fP, \fBeverything\fP }"
.br
.RI "\fIExpresses a verbosity level\&. \fP"
.in -1c
.SH "Enumeration Type Documentation"
.PP 
.SS "enum \fBverbosities\fP"

.PP
Expresses a verbosity level\&. Several classes report a different level of detail depending on the value of some internal verbosity variable, usually set with a function such as \fBDviFile#verbosity\fP\&.
.PP
The initial value of this is always \fCnormal\fP\&. The value \fCeverything\fP is the highest level (but not \fInecessarily\fP higher than \fCdebug\fP; the value \fCsilent\fP causes the class to produce no output at all\&.
.PP
The values are ordered, so that 
.PP
.nf

  enum verbosities verbosity_;
  \&.\&.\&.
  if (verbosity_ > normal) {
    // chatter
  }
.fi
.PP
 is a good way of testing whether the verbosity level is above normal\&. 
.PP
\fBEnumerator\fP
.in +1c
.TP
\fB\fIsilent \fP\fP
.TP
\fB\fIquiet \fP\fP
.TP
\fB\fInormal \fP\fP
.TP
\fB\fIdebug \fP\fP
.TP
\fB\fIeverything \fP\fP
.SH "Author"
.PP 
Generated automatically by Doxygen for dvi2bitmap from the source code\&.