C / C++ / MFC

salimhassan wrote:

...but same result getting assertion erors at run time

dubeypankaj wrote:

A Friend function can be avoided if get()(to read) and set()(to write) member functions(public) are provided on (private) data members of a class.
Is it True or False.

CString cs1 = L"Hello";
CString cs2 = L"World";
CString cs3 = L"";

cs3 = cs1 + L" World";
cs3 = L"Hello " + cs2;

dubeypankaj wrote:

you'll expose yourself to some very subtle bugs that have very subtle and often disastrous symptoms

VuNic wrote:

For example..

class Foo
{
  static const int N = 10;
  char * _buf;
public:
  Foo(char c){_buf = new char [N]; memset(_buf, c, N);}
  Foo & operator=(const Foo & foo)
  {
    if ( _buf )
    {
      delete _buf;
      _buf = new char[N];
    }
    memcpy(_buf, foo._buf, N);
    return *this;
  }
  Foo(const Foo & foo){...}
};

void main()
{
  Foo f('A');
  f = f;
}

CPallini wrote:

i.e. if you write it (implicitely) assuming it will be never used to do self-assignment.

led mike wrote:

And why would someone do that?

led mike wrote:

Isn't that considered Best Practice?

led mike wrote:

Or is this question about something entirely different than what I have been able to interpret?

led mike wrote:

And why would someone do that? Isn't that considered Best Practice? Or is this question about something entirely different than what I have been able to interpret?
It seems to me that it is about this subject[^]

CPallini wrote:

Nope, anyway it's a good candidate to be inserted into the WPF (Worst Practice Foundation).

CPallini wrote:

Sorry for the misunderstanding.

dubeypankaj wrote:

Thanx for the adjective used for me(Worst Practice Foundation user).

dubeypankaj wrote:

What are the problems associated with self assignment