#include <SimplifySum.h>

Public Types
enum	{ value = not ::boost::is_same< AB, base >::value }

typedef G	A

typedef Sum< A, B >::type	AB

typedef H	B

typedef SumStruct< A, B >	base

typedef F	C

Static Public Member Functions
static const A &	a (const F &f, const G &g, const H &h)

static const B &	b (const F &f, const G &g, const H &h)

static const C &	c (const F &f, const G &g, const H &h)

Detailed Description

template<typename F, typename G, typename H>
struct funct::SimplSumOrd< F, G, H >::prod2

Definition at line 154 of file SimplifySum.h.

Member Typedef Documentation

template<typename F, typename G, typename H>

typedef G funct::SimplSumOrd< F, G, H >::prod2::A

Definition at line 155 of file SimplifySum.h.

template<typename F, typename G, typename H>

typedef Sum< A , B >::type funct::SimplSumOrd< F, G, H >::prod2::AB

Definition at line 157 of file SimplifySum.h.

template<typename F, typename G, typename H>

typedef H funct::SimplSumOrd< F, G, H >::prod2::B

Definition at line 155 of file SimplifySum.h.

template<typename F, typename G, typename H>

typedef SumStruct< A , B > funct::SimplSumOrd< F, G, H >::prod2::base

Definition at line 156 of file SimplifySum.h.

template<typename F, typename G, typename H>

typedef F funct::SimplSumOrd< F, G, H >::prod2::C

Definition at line 155 of file SimplifySum.h.

Member Enumeration Documentation

template<typename F, typename G, typename H>

anonymous enum

Enumerator
value

Definition at line 161 of file SimplifySum.h.

161 { value = not ::boost::is_same< AB, base >::value };

value

Definition: value.py:1

relativeConstraints.value

value

Definition: relativeConstraints.py:52

Member Function Documentation

template<typename F, typename G, typename H>

static const A& funct::SimplSumOrd< F, G, H >::prod2::a	(	const F &	f,
		const G &	g,
		const H &	h
	)

inlinestatic

Definition at line 158 of file SimplifySum.h.

References g.

158 { return g; }

g

The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e g

Definition: Activities.doc:4

template<typename F, typename G, typename H>