| 1 | .TH ANSI2KNR 1 "19 Jan 1996" | 
|---|
| 2 | .SH NAME | 
|---|
| 3 | ansi2knr \- convert ANSI C to Kernighan & Ritchie C | 
|---|
| 4 | .SH SYNOPSIS | 
|---|
| 5 | .I ansi2knr | 
|---|
| 6 | [--varargs] 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 function definitions by seeing a non-keyword identifier at the left | 
|---|
| 14 | margin, followed by a left parenthesis, with a right parenthesis as the last | 
|---|
| 15 | character on the line, and with a left brace as the first token on the | 
|---|
| 16 | following line (ignoring possible intervening comments).  It will recognize a | 
|---|
| 17 | multi-line header provided that no intervening line ends with a left or right | 
|---|
| 18 | brace or a semicolon.  These algorithms ignore whitespace and comments, except | 
|---|
| 19 | that the function name must be the first thing on the line. | 
|---|
| 20 | .sp | 
|---|
| 21 | The following constructs will confuse it: | 
|---|
| 22 | .br | 
|---|
| 23 | - Any other construct that starts at the left margin and follows the | 
|---|
| 24 | above syntax (such as a macro or function call). | 
|---|
| 25 | .br | 
|---|
| 26 | - Some macros that tinker with the syntax of the function header. | 
|---|
| 27 | .sp | 
|---|
| 28 | The --varargs switch is obsolete, and is recognized only for | 
|---|
| 29 | backwards compatibility.  The present version of | 
|---|
| 30 | .I ansi2knr | 
|---|
| 31 | will always attempt to convert a ... argument to va_alist and va_dcl. | 
|---|
| 32 | .SH AUTHOR | 
|---|
| 33 | L. Peter Deutsch <ghost@aladdin.com> wrote the original ansi2knr and | 
|---|
| 34 | continues to maintain the current version; most of the code in the current | 
|---|
| 35 | version is his work.  ansi2knr also includes contributions by Francois | 
|---|
| 36 | Pinard <pinard@iro.umontreal.ca> and Jim Avera <jima@netcom.com>. | 
|---|