The QNX PPS Developer's Guide includes:
Throughout this manual, we use certain typographical conventions todistinguish technical terms. In general, the conventions we useconform to those found in IEEE POSIX publications. The following tablesummarizes our conventions:
|Code examples||if( stream == NULL )|
|File and pathnames||/dev/null|
|Keyboard input||something you type|
|Programming data types||unsigned short|
|Programming literals||0xFF, "message string"|
We use an arrow (→) in directions for accessing menuitems, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight importantmessages:
|Notes point out something important or useful.|
|Cautions tell you about commands or procedures that may haveunwanted or undesirable side effects.|
|Warnings tell you about commands or procedures that could bedangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash(/) as a delimiter in all pathnames,including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
At the top and bottom of our HTML docs, you'll see some or all of thesebuttons:
|Use this button:||To move:|
|To the previous part of the document.|
|“Up” in the document:
|To the keyword index.|
|To the next part of the document.|
To obtain technical support for any QNX product, visit theSupport areaon our website (www.qnx.com).You'll find a wide range of support options, including community forums.
Copyright © 2009, QNX Software Systems GmbH & Co. KG. All rights reserved.