It seems like the browser you are using has JavaScript disabled. As a result, the site will not function properly. We really want you to enable it so you may experience our site as we intended it. If you have no idea what we are talking about or if you need help, visit http://www.enable-javascript.com×
This website uses cookies. By continuing to browse this site you are agreeing to our use of cookies. Find out more on our cookie page.×

Oops, it seems like you're using an old browser that we do not fully support. If you're able to, please upgrade your browser here.×
This website uses cookies. By continuing to browse this site you are agreeing to our use of cookies. Find out more on our cookie page.×

Files:

Classification:

Caveats:

The most current entry is saved in a static structure. Copy it before
making further accesses.

On each call to either getutid() or
getutline(),
the routine examines the static structure
before performing more I/O. If the contents of the static
structure match what it's searching for, the function looks no
further. For this reason, to use getutline() to search for
multiple occurrences, zero out the
static area after each success, or getutline() will
return the same structure over and over again.

There's one
exception to the rule about emptying the structure before
further reads are done: the implicit read done by
pututline()
(if it finds that it isn't already at the correct
place in the file) doesn't hurt the contents of the static
structure returned by the
getutent(),
getutid() or
getutline() routines, if the user has just modified those contents
and passed the pointer back to pututline().

These routines use buffered standard I/O for input, but
pututline() uses an unbuffered nonstandard write to avoid
race conditions between processes trying to modify the
utmp and wtmp files.

1. Download the tools

Before you start developing, you'll need to visit the Downloads tab. Here you'll find downloads for the BlackBerry 10 Native SDK, BlackBerry 10 Device Simulator, and some other useful tools.

2. Try the sample apps

Now featuring a filter control, the Sample apps tab allows you to search for samples by name or by feature.

Select either the Core or Cascades radio buttons to display the samples relevant to you.

3. Educate yourself

The Documentation tab contains tons of examples, tutorials, and best practices to guide you along the path towards building an awesome app.

You can access all the documentation that you need in the left-hand navigation.

4. Start developing

The Reference tab is where you'll find essential details about how to use our APIs.

You can use the left-hand navigation to choose how you would like to browse the reference: by module, by topic, or alphabetically. If you have an idea of what you are looking for, start typing it in the Filter box.