NAME
what — identify
SCCS files (DEVELOPMENT)
SYNOPSIS
what |
[-s] file... |
DESCRIPTION
The what utility searches the given files
for all occurrences of the pattern that get(1) (see
get(1) ) substitutes for %Z% (@(#)) and writes to standard
output what follows until the first occurrence of one of the following:
" > newline \ NUL
OPTIONS
The what utility supports the XBD
specification,
Utility
Syntax Guidelines . The following option is supported:
- -s
- Quit after finding the first occurrence of the pattern in each file.
OPERANDS
The following operands are supported:
- file
- A pathname of a file to search.
STDIN
Not used.
INPUT FILES
The input files are of any file type.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of
what :
LANG- Provide a default value for the internationalisation variables that are
unset or null. If
LANGis unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined. LC_ALL- If set to a non-empty string value, override the values of all the other internationalisation variables.
LC_CTYPE- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments and input files).
LC_MESSAGES- Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
NLSPATH- Determine the location of message catalogues for the processing of LC_MESSAGES .
ASYNCHRONOUS EVENTS
Default.
STDOUT
The standard output consists of the following for each file operand:
"%s:\n\t%s\n", <pathname>,
<identification string>
STDERR
Used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
The following exit values are returned:
CONSEQUENCES OF ERRORS
Default.
APPLICATION USAGE
The what utility is intended to be used in
conjunction with the SCCS command get(1) , which
automatically inserts identifying information, but it can also be used where
the information is inserted by any other means.
When the string "@(#)" is included in a library routine in a shared library, it might not be found in an a.out file using that library routine.
EXAMPLES
If the C-language program in file f.c contains:
char ident[] = "@(#)identification information";
and
f.c is compiled to
yield f.o
and a.out then the command: what f.c f.o
a.out
will write: f.c: identification information ...
f.o: identification information ... a.out: identification information
...
FUTURE DIRECTIONS
None.
SEE ALSO
get(1) .