check(1)

PROGRAM
check - checks the dates on a program and prog file

SYNTAX

check

-name
    name of program to check

[-config]
    use configuration file?

[-V]
    Gives the version for check

[-U]
    Gives the usage for check

[-P]
    Prompts for command line options

[-A [file1]]
    Creates the answer file called check.ans or file1

[-a [file1]]
    Uses check.ans or file1 as the answer file

DESCRIPTION

The purpose of ghostcheck is to check the dates on C source code and man pages versus the dates on *.prog and *.pane files for the application program that was generated using ghostreader and ghostwriter. It will give you a listing of the files with their dates, and give reasonably accurate advice about how to best bring files up to date.

NOTE: ghostcheck will not fail to give you advice, even if all files actually ARE up to date, since the only information it has to go on is the date at which each of the files were most recently modified. For instance, suppose you create .prog file file and generate C code from it which is also correct. If you then run ghostcheck, ghostcheck will tell you that the .prog file may need to be updated using ghostreader, even though the .prog file actually IS up to date. This is because the .prog file was created earlier than the C code.

Ghostcheck compares the dates of:
1) the main driver (*.c) file
2) the include (*.h) file
3) the man1 (*.1) page
4) the library (l*.c) file
5) the man3 (*.3) page
6) the PS (*.prog) file
7) the UIS (*.pane) file

REQUIRED ARGUMENTS

-name
    type: string
    desc: name of program to check

OPTIONAL ARGUMENTS

-config
    type: boolean
    desc: use configuration file?
    default: false

EXAMPLES

SEE ALSO
intro(1), verror(3), vgparms(3), vutils(3) ghostreader(1), ghostwriter(1)

RESTRICTIONS
The [-config] flag is optional, and is provided for the convenience of those who are maintaining code in /src, where there may be as many as 6 different locations for the 7 input files. By using the configuration file, you may specify a location for each input file. Use of a tilda '~' is allowed, as is the use of environment variables and toolbox names, such as $EXAMPLE_TOOLBOX.

COPYRIGHT
Copyright 1991, University of New Mexico. All rights reserved.