Containers_module

More...

Modules
	Containers_module_internal_classes
	Internal Containers_module classes and functions.

Classes
class	casacore::ArrayInitPolicy
	More...
struct	casacore::Allocator_private::AllocSpec< T >
	Allocator specifier. More...
struct	casacore::AllocSpec< T >
	Allocator specifier. More...
class	casacore::BlockTrace
	More...
class	casacore::Block< T >
	simple 1-D array More...
class	casacore::PtrBlock< T >
	A drop-in replacement for Block<T*>. More...
struct	casacore::BlockIO_global_functions_BlockIO
	More...
class	casacore::IterError
	More...
class	casacore::IterBoundaryError
	Iteration Boundary error class. More...
class	casacore::IterInitError
	Iteration initialization error. More...
class	casacore::InvalidIterError
	Invalide iteration error class. More...
class	casacore::ObjectStack< T >
	More...
class	casacore::Record
	More...
class	casacore::RecordDesc
	More...
class	casacore::RecordFieldPtr< T >
	More...
class	casacore::RORecordFieldPtr< T >
	Read-Only access to an individual field from a Record. More...
class	casacore::RecordFieldId
	More...
class	casacore::RecordInterface
	More...
class	casacore::ValueHolder
	More...

Detailed Description

Non-mathematical Containers

See below for an overview of the classes in this module.

Review Status

Reviewed By:

UNKNOWN

Date Reviewed:

before2004/08/25

Synopsis

This module provides non-mathematical containers. These containers are the prototypical computer science types of containers – records and simple arrays. These classes are useful for all of the various types of low level data management. In general, these classes will have familiar semantics and an unsurprising interface. Note that Casacore used to have classes such as Map and List, but they became obsolete when the Standard C++ Library was introduced. Therefore these classes have been removed.

Most of the important classes in this module also have IO shift operators, e.g. for writing out a Block (simple array). These operators typically allow the container (and the objects it contains) to be written out to both AipsIO and the standard ostream.

The class Block has the option to trace (de)allocations for Blocks with a size above a given threshold. It uses class MemoryTrace to log the trace messages. Unlike MemoryTrace, it also works on non-Linux systems. Since class Array uses Block underneath, it makes it possible to trace Array usage.