About This Guide

The QNX PPS Developer's Guide includes:

Typographical conventions

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:

Reference Example
Code examples if( stream == NULL )
Command options -lR
Commands make
Environment variables PATH
File and pathnames /dev/null
Function names exit()
Keyboard chords Ctrl-Alt-Delete
Keyboard input something you type
Keyboard keys Enter
Program output login:
Programming constants NULL
Programming data types unsigned short
Programming literals 0xFF, "message string"
Variable names stdin
User-interface components Cancel

We use an arrow (→) in directions for accessing menuitems, like this:

You'll find the Other... menu item underPerspective-->Show View.

We use notes, cautions, and warnings to highlight importantmessages:

Note: Notes point out something important or useful.

Caution: Cautions tell you about commands or procedures that may haveunwanted or undesirable side effects.

WARNING: Warnings tell you about commands or procedures that could bedangerous to your files, your hardware, or even yourself.

Note to Windows users

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.

Technical support options

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–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.