Copyright (c) 1980 The Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

@(#)vgrind.1 6.3 (Berkeley) 10/25/88

C 4 vgrind - grind nice listings of programs vgrind [ -f ] [ - ] [ -t ] [ -n ] [ -x ] [ -W ] [ -sn ] [ -h header ] [ -d file ] [ -l language ] name ... Vgrind formats the program sources which are arguments in a nice style using troff (1) Comments are placed in italics, keywords in bold face, and the name of the current function is listed down the margin of each page as it is encountered.

Vgrind runs in two basic modes, filter mode or regular mode. In filter mode vgrind acts as a filter in a manner similar to tbl (1). The standard input is passed directly to the standard output except for lines bracketed by the troff-like macros:

- starts processing - ends processing

These lines are formatted as described above. The output from this filter can be passed to troff for output. There need be no particular ordering with eqn (1) or tbl (1).

In regular mode vgrind accepts input files, processes them, and passes them to troff (1) for output.

In both modes vgrind passes any lines beginning with a decimal point without conversion.

The options are:

forces filter mode forces input to be taken from standard input (default if -f is specified ) similar to the same option in troff causing formatted text to go to the standard output forces no keyword bolding outputs the index file in a ``pretty'' format. The index file itself is produced whenever vgrind is run with a file called index in the current directory. The index of function definitions can then be run off by giving vgrind the -x option and the file index as argument. forces output to the (wide) Versatec printer rather than the (narrow) Varian specifies a point size to use on output (exactly the same as the argument of a .ps) specifies a particular header to put on every output page (default is the file name) specifies an alternate language definitions file (default is /usr/lib/vgrindefs) specifies the language to use. Currently known are PASCAL ( -lp ), MODEL ( -lm ), C ( -lc or the default), CSH ( -lcsh ), SHELL ( -lsh ), RATFOR ( -lr ), MODULA2 ( -lmod2 ), YACC ( -lyacc ), ISP ( -lisp ), and ICON ( -lI ). index file where source for index is created

/usr/lib/tmac/tmac.vgrind macro package

/usr/lib/vfontedpr preprocessor

/usr/lib/vgrindefs language descriptions

Dave Presotto & William Joy vlp(1), vtroff(1), vgrindefs(5) Vfontedpr assumes that a certain programming style is followed:

For 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.

For PASCAL - function names need to appear on the same line as the keywords function or procedure.

For MODEL - function names need to appear on the same line as the keywords is beginproc.

If these conventions are not followed, the indexing and marginal function name comment mechanisms will fail. More generally, arbitrary formatting styles for programs mostly look bad. The use of spaces to align source code fails miserably; if you plan to vgrind your program you should use tabs. This is somewhat inevitable since the font used by vgrind is variable width.

The mechanism of ctags in recognizing functions should be used here.

Filter mode does not work in documents using the -me or -ms macros. (So what use is it anyway?)