src/usr.bin/vgrind/vgrind.1 - diff

Return to vgrind.1 CVS log

Up to [local] / src / usr.bin / vgrind

Diff for /src/usr.bin/vgrind/Attic/vgrind.1 between version 1.6 and 1.7

version 1.6, 2000/03/06 03:17:40

version 1.7, 2000/03/14 14:58:25

Line 65

.Nm

runs in two basic modes, filter mode (see the

.Fl f

option) or regular mode. In filter mode

option) or regular mode.

In filter mode

.Nm

acts as a filter in a manner similar to

.Xr tbl 1 .

Line 80

Line 81

ends processing

.El

.Pp

These lines are formatted as described above. The output from this

These lines are formatted as described above.

filter can be passed to

The output from this filter can be passed to

.Xr troff 1

for output. There need be no particular ordering with

for output.

There need be no particular ordering with

.Xr eqn 1

.Xr tbl 1 .

Line 117

Line 119

Specifies a particular header to put on every output page (default is

the file name).

.It Fl l

Specifies the language to use. Currently known are

Specifies the language to use.

Currently known are

.Tn PASCAL

.Pq Fl l Ns Ar p ,

.Tn MODEL

Line 194

Line 197

For

.Tn C

\- function names can be preceded on a line only by spaces, tabs, or an

asterisk. The parenthesized arguments must also be on the same line.

asterisk.

The parenthesized arguments must also be on the same line.

.Pp

For

.Tn PASCAL

Line 214

Line 218

More generally, arbitrary formatting styles for programs mostly look bad.

The use of spaces to align source code fails miserably; if you plan to

.Nm

your program you should use tabs. This is somewhat inevitable since the

your program you should use tabs.

font used by

This is somewhat inevitable since the font used by

.Nm

is variable width.

.Pp