Rogue Wave documentation uses the following conventions.
The Rogue Wave SourcePro C++ products use special pathname conventions. These are summarized in Table 3:
Documentation for the SourcePro C++ products uses special typographic conventions. These conventions are summarized in Table 4:
Conventions | Purpose | Example |
courier | Function names, code, directories, file names, examples, operating system commands, URLs. | RWWinSockInfo info; cout << "Error Processing:" Visit us at www.roguewave.com |
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 |
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.