First what is the difference when using
MyClass mc(val); vs using
MyClass *mc = new MyClass(val);
2nd question.
If I put the declartion of the classes in a loop the "MyClass mc(val)" will cause stack overflow problems where the second doesn't. I have my own thoughts, but wanted to see if I van get more info. Thank you to who respond.
Shawn
Hmm.. I don't know about stack overflow, but the second one allocates new memory for the class, and should be freed at the end of the program, or else a memory leak has been born.
Compilers:
GCC on Red Hat 8.1 (Primary)
GCC on Mac OS X 10.2.4 (Secondary)
Others:
MinGW on XP
Another question, Will the two diffrent declarations have an effect on Constructer use? Will one way allow for diffrent things. For example if I had several types of Constricters for that class whould they be effected by the type of declartion.
To answer that question, you need to give us (me) some examples of situations in which you use it, and we may bew able to tell you if that will allow you to use it in different wats.
~Inquirer
Compilers:
GCC on Red Hat 8.1 (Primary)
GCC on Mac OS X 10.2.4 (Secondary)
Others:
MinGW on XP
What I am wanting is how the Constructer is used with the two diffrent declartions. Does the Constructer react diffrent when used in the contex of MyClass mc(val) vs when the Constructer is used in the contex of MyClass * mc = new MyClass(val); Just looking for information on constructer use? Does this give more information to answer my question. Thank you.
Oh, IC. No, the constructor won't react differently. The only thing that is different, is that the first won't specifically aallocate any memory, but the second wil. AND, THIS MEMORY MUST BE FREED.
~InquirerCode:char *c = new char[10000]; delete [] c; // Do this or else huge memory leak
Compilers:
GCC on Red Hat 8.1 (Primary)
GCC on Mac OS X 10.2.4 (Secondary)
Others:
MinGW on XP
