Class Array0 is a c-style array wrapper that does bounds checking in debug mode. It indexes from 0 just like regular c-arrays. Class Array0 does not manage it's own memory. It does not allocate memory if you want to make it larger, nor does it deallocate memory when you destroy it. Bounds checking only ensures that the user does not go outside of the memory Array0 thinks it's in charge of. If the user should happen to point the array0 at memory that has not been allocated, Array0 is not responsible for segmentation fault that will likely occur. Garbage in, garbage out. More...

#include <ArrayPool.hh>

Public Member Functions
	Array0 ()
	Default ctor points at null. More...

	Array0 (T *mem_begin, platform::Size size)
	Array and size constructor – point this Array0 at a block of memory. More...

	Array0 (Array0< T > const &other)
	Copy constructor – point this Array0 at a block of memory. More...

Array0< T > const &	operator= (Array0< T > const &rhs)
	Assignment operator – point this Array0 at a different block of memory. More...

	~Array0 ()=default
	The destructor does not deallocate the memory that this Array0 points at. That is the responsibility of some other class. Array0 is for bounds checking only. More...

T &	operator[] (platform::Size index)
	Accessors and mutators. More...

T const &	operator[] (platform::Size index) const

T &	operator[] (int index)

T const &	operator[] (int index) const

platform::Size	size () const

Private Member Functions
bool	bounds_check (platform::Size index) const

bool	bounds_check (int index) const

Private Attributes
T *	array_

platform::Size	size_

Detailed Description

template<class T>
class utility::graph::Array0< T >

Class Array0 is a c-style array wrapper that does bounds checking in debug mode. It indexes from 0 just like regular c-arrays. Class Array0 does not manage it's own memory. It does not allocate memory if you want to make it larger, nor does it deallocate memory when you destroy it. Bounds checking only ensures that the user does not go outside of the memory Array0 thinks it's in charge of. If the user should happen to point the array0 at memory that has not been allocated, Array0 is not responsible for segmentation fault that will likely occur. Garbage in, garbage out.

Constructor & Destructor Documentation

◆ Array0() [1/3]

template<class T >

utility::graph::Array0< T >::Array0 ( )

inline

Default ctor points at null.

◆ Array0() [2/3]

template<class T >

utility::graph::Array0< T >::Array0	(	T *	mem_begin,
		platform::Size	size
	)

inline

Array and size constructor – point this Array0 at a block of memory.

◆ Array0() [3/3]

template<class T >

utility::graph::Array0< T >::Array0 ( Array0< T > const & other )

inline

Copy constructor – point this Array0 at a block of memory.

◆ ~Array0()

template<class T >

utility::graph::Array0< T >::~Array0 ( )

default

The destructor does not deallocate the memory that this Array0 points at. That is the responsibility of some other class. Array0 is for bounds checking only.