This manual, the C User's Guide describes the C 4.2 compiler. The standard language is referred to as ANSI C. The notation K&R C refers to Kernighan and Ritchie C, which is non-ANSI (or pre-ANSI) C.

Chapter 1, "Introduction to the C Compiler," provides an overview to C.

Chapter 2, "cc Compiler Options," describes the compiler optionsfor the Solaris^TM operating system.

Chapter 3, "Sun ANSI C Compiler-Specific Information," describes areas specific to the Sun ANSI C compiler.

Chapter 4, "Cscope: Interactively Examine a C Program," describes cscope, a C programming tool.

Chapter 5, Lint Source Code Checker," describes how to use lint, another C programming tool.

This book also includes these appendices:

• Appendix A, "ANSI C Data Representations"
• Appendix B, "Implementation-Defined Behavior"
• Appendix C, "-Xs Differences for Sun C and ANSI C"
• Appendix D, "Performance Tuning (SPARC)"

Online Documentation

• Online books
• Man pages (ASCII, formatted with nroff)
• Error and Warning Messages file (ASCII)
• C 4.x README file (ASCII)
• PostScript files

• Take advantage of dynamically linked headings and cross-references.
• Search for topics by using a word or phrase.

The following C compiler documentation is provided in online books:

• C User's Guide--Describes the features of the C 4.x compiler.
• Making the Transition to ANSI C--Shows how to port your C code from previous versions of C to ANSI C.

To view a man page using the man command:

1. Insert the name of the directory in which you installed the C compiler at the beginning of your search path.

2. Add a line to the .cshrc file with setenv MANPATH= at the start or, to the .profile file with export MANPATH= at the start.

3. Now, view a man page by executing this command:

% man command_name

Table P-2 describes the C man pages, and identifies the best uses for each man page.

Table  P-2 C Man Pages and their Usage

Title	Description	Usage
cb	Formats your source code.	Makes the program more readable.
cc	Describes the C compilation system.	Provides C system information.
cflow	Produces a flow graph of the external references in C, lex, yacc, and assembly-language files.	Checks program dependencies.
cscope	Interactively examines a C program.	Searches and edits source files.
ctrace	Traces C program execution, statement by statement.	Checks program execution statements.
cxref	Generates a C program cross-reference table.	Checks program dependencies and structure.
c89	Enables compliance with XPG4.	Verifies XPG4 comopliance.
indent	Indents and formats a C program source file.	Indents and formats source file.
lint	The C program checker.	Checks for code constructs that may cause the program to not compile or execute with unexpected results. Also checks program portability and cross-file consistency.

Table P-3 Identifies the man pages containing C compiler related information.

Table  P-3 C-Related Man Pages 

Title	Description
gprof	Includes the prof functionality, and produces a callgraph profile displaying a list of modules that call, or are called by, other modules.
ild	Contains information on the incremental ild linker.
inline	Contains information on inlining code.
m4	Preprocesses C and assembly language programs.
make	Maintains, updates, and regenerates related programs and files.
ld	Contains information on the ld linker.
lex	Describes the lexical analysis program generator.
prof	Reports time, percentage of time spent executing a program and number of calls to functions.
sccs	Provides a front end for the source code control system.
tcov	Provides a line-by-line frequency profiler that produces a copy of the source file, annotated to show which lines are used, and how often.
yacc	Parses tokens passed by a lexical analyzer.

The man man page describes the options available with the man command to browse man pages. Other tools, such as tkman, provide search features and hypertext links to the man pages listed in the "SEE ALSO" section of a man page.

To print man pages with the lp command, type:

% man command_name | lp

Error and Warning Messages File

There are several methods to locate an error message and its description in the file:

• Load the ASCII file into an editor and use the editor commands to search the file.
• Use the grep command in a shell to search the file.
• Use the command cc -xhelp=errors to view the file.

file: filename line: n  empty constant expression after macro expansion

1. Loading the /opt/SUNWspro/READMEs/c_lint_errors file into an editor.

2. Searching for a string from the message, for example, "empty constant."

empty constant expression after macro expansion

A #if or #elif directive contains an expression that, after macro 
expansion, consists of no tokens.

#define EMPTY

#if EMPTY

     char *mesg = "EMPTY is non-empty";

#end if

MESSAGE ID: E_EMPTY_CONST_EXP_AFTER_EXPAND

-----------------------------------------

To print the Error and Warning Messages file, type:

% lp /opt/SUNWspro/READMEs/c_lint_errors

---

Note - The compiler displays many of the messages contained in this file only when used with the cc -v option. With this option, the compiler performs stricter semantics checking and, therefore, displays more diagnostic messages.

---

• New features in this release
• Changes to features
• Software incompatibilities
• Current software bugs
• Documentation errata

PostScript Files

To view a PostScript file online, type:

% imagetool filename &

% lp filename

• C User's Guide, describes the features accompanying the C 4.2 compiler.

• C 4.2 Quick Reference, summarizes the command-line options.

• The platform-specific installation guides, containing instructions for installing the C compiler and other software on Solaris; as well as information on licensing.

• Performance Profiling Tools--Provides information on various profiling tools, such as prof. Available in online books.

• Numerical Computation Guide--Describes floating-point software and hardware. Available in online books.

• Linker and Libraries Guide--Provides information on the linker, ld, and on linking libraries. See also the ld(1) man page. Part of the Solaris programming documentation.

• Incremental Link Editor (ild)--Provides information on the incremental linker, ild, which replaces the standard linker for incremental linking.

• The C Language, second edition, by Kernighan and Ritchie (Prentice-Hall, 1988)

• C: A Reference Manual, third edition, by Harbison and Steele (Prentice-Hall, 1991)

• The Standard C Library, by P. J. Plauger (Prentice-Hall, 1992)

Typographic Conventions

machine_name% You have mail.

Table P-5 describes the typographic notations used for arguments to the compiler and lint tool options.

Table  P-5 Typographic Notations for Arguments  

Notation	Meaning	Example
[ ]	Square brackets contain arguments that can be optional or required.	-d[y|n]
|	The "pipe" or "bar" symbol separates arguments, only one of which may be used at one time.	-d[y|n]
,	The comma separates arguments, one or more of which may be used at one time.	-xinline=[f1,...fn]
:	The colon, like the comma, is sometimes used to separate arguments.	-Rdir[:dir]
...	The ellipsis indicates omission in a series.	-xinline=[f1,...fn]
%	The percent sign indicates the word following it has a special meaning.	-ftrap=%all
`	The back quote indicates a command that is being executed.	`uname -s`

Other Documentation Conventions

• The Solaris^TM 2.x operating system on the following architectures:

  • SPARC^TM architectures

  • Intel architectures, where Intel refers to the Intel implementation of one of the following: Intel 80386, Intel 80486, Pentium, or the equivalent

  • The RISC PowerPC architecture compliant with the Common Hardware Reference Platform (CHRP) and the PowerPC Reference Platform (PReP) specifications

Path Names

Shell Prompts in Command Examples

$

#