mfc, C++ Question

by **Practical Soul** » Tue, 01 Jul 2003 12:26:34 GMT

Hi,

Iam using a MS Flexgrid to display some information. I
have derived a class called "CGrid" from "CMSFlexGrid".
Now, my problem is that while I can access all the public
methods of CMSFlexgrid in CGrid, Iam not able to add and
use any new member variables in my derived class, CGrid.
Any idea why? Pls see the code snippet for the class
declaration.

#include "msflexgrid.h"

class CGrid : public CMSFlexGrid
{
public: //Member functions
void SetHeader(int nCol, CString strText);
void Refresh();
void InsertRowAtTop();
void AppendRow();
void SetCellText(int nRow, int nCol, CString
strText);
void Init(void);
void SetDefaultProperties(void);
void SortGrid(void);
CGrid();
virtual ~CGrid();

private: //Member variables
int m_Rows;
int m_Cols;
int m_nSortOrder;
};

It throws a run-time error when I set the values of the
private member variables in the member functions of
CGrid. When I comment out the statements, it works fine.

by **MFC** » Mon, 29 Aug 2005 01:03:09 GMT

I want to set all the member variables of a C++ object to 0, Can I do
memset(this , 0 , sizeof(*this)) in the constructor?

by **David Lowndes** » Mon, 29 Aug 2005 02:47:10 GMT

>I want to set all the member variables of a C++ object to 0, Can I do

Not generally.

If your class is composed of plain old data members only (and has no
virtual methods), then you could, but I'd recommend that you
initialise each variable (that needs explicitly initialising)
individually.

Dave
--
MVP VC++ FAQ: http://www.mvps.org/vcfaq

by **skasat@gmail.com** » Thu, 23 Mar 2006 08:19:37 GMT

I was just going thru some changes in my code and need to write some
thing like this

try{
//some code
//if error
return
}

catch{}

I had a doubt using return statement in my try block...what impact will
it have...

by **Dan Bloomquist** » Thu, 23 Mar 2006 10:53:35 GMT

Of course, the reason for putting 'some code' in a 'try is because
methods of that code are capable of 'throwing. It is a cheap way of
unwinding the stack on an error. If you get to 'if error' then there was
nothing to 'catch and you can return. If the underlying code throws you
will never get to the 'if error'. It will surface at the 'catch. It will
be some other error that you know about at 'if error'. In either case
the stack is even at that point and you can return. It is common to:

try
{
if(...)
return true | false;
//or fall threw past 'catch
}
catch(.. e )
{
...//Warn?
e->Delete( );
return false;
}
return true;

Best, Dan.

--
"We need an energy policy that encourages consumption"
George W. Bush.

"Conservation may be a sign of personal virtue, but it is not a
sufficient basis for a sound, comprehensive energy policy."
Vice President Dick Cheney

by **Tom Serface** » Thu, 23 Mar 2006 11:42:24 GMT

Doesn't make any difference at all if no exceptions are thrown.

Tom

mfc, C++ Question

mfc >> C++ Question

mfc >> C++ question

mfc >> C++ question

C++ question

C++ question

C++ question