[cfd] / ansi2knr.1

.TH ANSI2KNR 1 "31 December 1990" 
.SH NAME
ansi2knr \- convert ANSI C to Kernighan & Ritchie C
.SH SYNOPSIS
.I ansi2knr
input_file output_file
.SH DESCRIPTION
If no output_file is supplied, output goes to stdout.
.br
There are no error messages.
.sp
.I ansi2knr
recognizes functions by seeing a non-keyword identifier at the left margin, followed by a left parenthesis, with a right parenthesis as the last character on the line.  It will recognize a multi-line header if the last character on each line but the last is a left parenthesis or comma.  These algorithms ignore whitespace and comments, except that the function name must be the first thing on the line.
.sp
The following constructs will confuse it:
.br
     - Any other construct that starts at the left margin and follows the above syntax (such as a macro or function call).
.br
     - Macros that tinker with the syntax of the function header.
Commit	Line	Data
b91e2391	1	.TH ANSI2KNR 1 "31 December 1990"
	2	.SH NAME
	3	ansi2knr \- convert ANSI C to Kernighan & Ritchie C
	4	.SH SYNOPSIS
	5	.I ansi2knr
	6	input_file output_file
	7	.SH DESCRIPTION
	8	If no output_file is supplied, output goes to stdout.
	9	.br
	10	There are no error messages.
	11	.sp
	12	.I ansi2knr
	13	recognizes functions by seeing a non-keyword identifier at the left margin, followed by a left parenthesis, with a right parenthesis as the last character on the line. It will recognize a multi-line header if the last character on each line but the last is a left parenthesis or comma. These algorithms ignore whitespace and comments, except that the function name must be the first thing on the line.
	14	.sp
	15	The following constructs will confuse it:
	16	.br
	17	- Any other construct that starts at the left margin and follows the above syntax (such as a macro or function call).
	18	.br
	19	- Macros that tinker with the syntax of the function header.