Typographic Conventions

Documentation for the SourcePro products uses special typographic conventions. These conventions are summarized in Table 4:

Table 3 – Typographic conventions
Conventions	Use	Example
courier	Function names, code, directories, file names, examples, operating system commands, URLs.	RWWinSockInfo info; cout << “Error Processing:” Visit us at https://www.perforce.com/products/sourcepro.
italic	Conventional uses, such as new terms and titles.	Functors, or function objects Essential Tools Module Reference Guide
bold italic	Class names, emphasis, and some subheads.	RWCollectable
bold	Conventional uses, such as emphasis. Commands from an interface.	You should always read the manual. Click the OK button
ellipsis	Indicates part of the code is missing from an example.	foo(){ ... //something happens }
pathnames / or \	When the context for a pathname could be either Windows or UNIX, the path is written with a Windows “\” separator.	Windows path: buildspace\sproenv_vars.bat UNIX path: buildspace/sproenv_vars.sh OS-neutral path: <buildspace>\docs\index.html