C / C++ / MFC

//header.h
	CMyObject();
	CMyObject(const CMyObject &obj);		// Copy operator
	CMyObject& operator= (const CMyObject &obj);	// Assigment Operator
	BOOL operator== (const CMyObject &obj);		// Equalty operator
	virtual ~CMyObject();

CMyObject::CMyObject()
{	m_dVar1 = 0.0;
	m_bVar2 = FALSE;
	//and so on
}

//***********

CMyObject::CMyObject(const CMyObject &obj)
{	m_dVar1 = obj.m_dVar1;
	m_bVar2 = obj.m_bVar2;
	// and one more for every member variable that the class owns
}

//***********

CMyObject& CMyObject::operator= (const CMyObject &obj)
{	m_bVar1 = obj.m_bVar1;
	m_bVar2 = obj.m_bVar2;
	// and one more for every member variable that the class owns
	return *this;
}

//***********

BOOL CMyObject::operator== (const CMyObject &obj)
{	return ((this->m_bVar1 == obj.m_bVar1) && 
		(this->m_bVar2 == obj.m_bVar2) &&
	// and one more for every member variable that the class owns
		);
}

//***********

CMyObject::~CMyObject()
{
//if the object has lists or arrays, delete the contents...
//free possible used memory...
}

Greetings.

--------
M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?

Help me to understand what I'm saying, and I'll explain it better to you

“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson

pagePathArray( pagePathArray& rhs )
{
   m_memberOne = rhs.m_memberOne;
   ...
}

void COpenFolderPage::GetPagesPath( CArray<type,type>& pagePathArray )
{
}

CArray<type, type> COpenFolderPage::GetPagesPath()
{

CArray<type, type> pagePathArray;


// some code

return pagePathArray;
}

const CArray<type, type>& COpenFolderPage::GetPagesPath()

CPallini wrote:

I know, I'm quite polemical, cheers

bool COpenFolderPage::GetPagesPath(CArray < type, type > & pagePathArray )
{
  bool success;

  // some code using pagePathArray
 
  return success;
}

jhwurmbach wrote:

E.g. the function could need a very large temporary array in its algorithm.
This would then enlarge the callers array, without shrinking it, like a copy would do.

jhwurmbach wrote:

Because the board software eats all >...

jhwurmbach wrote:

OK, I might have used the wrong word...

jhwurmbach wrote:

What are < > called, then?

VC_RYK wrote:

...if i have to create this key then what value should be assigned against this key.