CLAM::BinaryControlOpConfig Class Reference

#include <BinaryControlOp.hxx>

List of all members.

Public Member Functions
	BinaryControlOpConfig ()
	BinaryControlOpConfig (const BinaryControlOpConfig &prototype, const bool shareData=false, const bool deep=true)
	__COMMON_DYNAMIC_TYPE (BinaryControlOpConfig, 1)
	__COMMON_DYN_ATTRIBUTE (0, public, std::string, Name) protected
bool	LoadName (CLAM::Storage &s)
Protected Member Functions
void	DefaultInit ()
	The concrete dynamic type constructor calls DefaultInit().

---

Detailed Description

Definition at line 31 of file BinaryControlOp.hxx.

---

Constructor & Destructor Documentation

CLAM::BinaryControlOpConfig::BinaryControlOpConfig

(

)

[inline]

Definition at line 30 of file BinaryControlOp.hxx.

CLAM::BinaryControlOpConfig::BinaryControlOpConfig	(	const BinaryControlOpConfig &	prototype,
		const bool	shareData = false,
		const bool	deep = true
	)			[inline]

Definition at line 30 of file BinaryControlOp.hxx.

---

Member Function Documentation

CLAM::BinaryControlOpConfig::__COMMON_DYN_ATTRIBUTE	(	0	,
		public	,
		std::string	,
		Name
	)			[inline]

Definition at line 31 of file BinaryControlOp.hxx.

CLAM::BinaryControlOpConfig::__COMMON_DYNAMIC_TYPE	(	BinaryControlOpConfig	,
		1
	)

void CLAM::BinaryControlOpConfig::DefaultInit

(

void

)

[inline, protected]

The concrete dynamic type constructor calls DefaultInit().

This allows user to initialize his/her object. But we define DefaultInit() here because we don't want to force writting one DefaultInit() function for each concrete dynamic type. If a dynamic type concrete class defines some (not-default) constructors, this should also call the DefaultInit().

See also:

CopyInit()

Reimplemented from CLAM::DynamicType.

Definition at line 35 of file BinaryControlOp.hxx.

bool CLAM::BinaryControlOpConfig::LoadName

(

CLAM::Storage &

s

)

[inline]

Definition at line 31 of file BinaryControlOp.hxx.

---

The documentation for this class was generated from the following file:

• BinaryControlOp.hxx