RealView Libraries and Floating Point Support Guide
Home Products Events Support	Search Keil.com for:

Technical Support

On-Line Manuals

RealView Libraries and Floating Point Support Guide

The C and C++ Libraries

About the C and C++ libraries

Features of the C and C++ libraries

Namespaces

Writing reentrant and thread‑safe code

Introduction to reentrancy and thread‑safety

Use of static data in the C libraries

The __user_libspace static data area

Managing locks in multithreaded applications

Using the ARM C libraries with a multithreaded app

Thread‑safety in the ARM C libraries

Thread‑safety in the ARM C++ libraries

Building an application with the C library

Using the libraries with an application

Building an application for a semihosted environme

Building an application for a non semihosting envi

Building an application without the C library

Integer and FP helper functions

Bare machine integer C

Bare machine C with floating‑point

Exploiting the C library

The standalone C library functions

Tailoring the C library to a new execution environ

How C and C++ programs use the library functions

Exiting from the program

__rt_lib_init()

__rt_lib_shutdown()

Tailoring static data access

Tailoring locale and CTYPE using assembler macros

Selecting locale at link time

Selecting locale at runtime

Defining a locale block

LC_CTYPE data block

LC_COLLATE data block

LC_MONETARY data block

LC_NUMERIC data block

LC_TIME data block

The lconv structure

Tailoring locale and CTYPE using C macros

Selecting locale at link time

Selecting locale at runtime

Macros and utility functions

_get_lc_ctype()

_get_lc_collate()

_get_lc_monetary()

_get_lc_numeric()

__LC_COLLATE_DEF

__LC_NUMERIC_DEF

__LC_MONETARY_DEF

The lconv structure

Tailoring error signaling, error handling, and pro

__rt_errno_addr()

__default_signal_handler()

__rt_fp_status_addr()

Tailoring storage management

Avoiding the ARM‑supplied heap and heap‑using

Support for malloc

Tailoring the runtime memory model

The memory models

Controlling the runtime memory model

Writing your own memory model

__user_initial_stackheap()

__user_setup_stackheap()

__user_heap_extend()

__user_heap_extent()

__user_stack_cleanup_space()

__rt_heap_extend()

__rt_stack_postlongjmp()

Tailoring the input/output functions

Dependencies on low‑level functions

Target‑dependent input/output support functions

_sys_command_string()

#pragma import(_main_redirection)

Tailoring other C library functions

Selecting real‑time division

ISO implementation definition

ISO C library implementation definition

Standard C++ library implementation definition

C library extensions

Library naming conventions

Placing ARM libraries

Helper libraries

Identifying library variants

The C Micro-library

Floating‑point Support

Namespaces

RealView^® Compilation Tools for µVision Libraries and Floating Point Support Guide

Version 3.1

Home > The C and C++ Libraries > About the C and C++ libraries > Namespaces

2.1.2. Namespaces

All C++ standard library names, including the C library names, if you include them, are defined in the namespace std using the following C++ syntax:

#include <cstdlib> // instead of stdlib.h

This means that you must qualify all the library names using one of the following methods:

specify the standard namespace, for example:
```
std::printf("example\n");
```
use the C++ keyword using to import a name to the global namespace:
```
using namespace std;
printf("example\n");
```
use the compiler option ‑‑using_std.

Note

errno is a macro, so it is not necessary to qualify it with a namespace.

Copyright © 2007 ARM Limited. All rights reserved.	ARM DUI 0378A
PDF version

Home > The C and C++ Libraries > About the C and C++ libraries > Namespaces