In C++ programming, suppose that you've implemented a class called FGH and that it has only one private member variable, a pointer x that points to an object of another class called JKL. It is not stated in particular here what problems FGH or JKL are intended to solve, nor the reason why FGH is storing the pointer x in a member variable. (To avoid biasing your answer to the questions below, I'm not specifying these things, because the questions ask you to explore various possibilities, focusing on why we would make certain design decisions instead of others.) Given these assumptions and no others, answer the following questions about them.
Under what circumstances would it be necessary to implement a destructor in the class FGH? Under what circumstances would it be fine to leave it out?
Suppose you felt that you needed to implement a destructor in FGH. Under what circumstances would it also be necessary to implement a copy constructor in the class FGH? Under what circumstances would it be fine to leave it out?
Suppose you felt that you needed to implement a destructor in FGH. Under what circumstances would it also be necessary to overload the assignment operator in the class FGH? Under what circumstances would it be fine not to overload it?

My favorite is "be concise."have you ever received an email and had to read a page full of information? by the time you finished reading it, you had to re-read it? i have even hit "reply" so that i could break it down into separate paragraphs and send it back to myself.what is concise? get to the point, fast. when opening an email like this, some will close it or print it to read later.i learned to use the subject line to prepare the reader for content. such as, "need on (blank), " "info only re: (blank)," "request input on (blank)," "read before (blank) meeting." these are just some.if you are asking for something, make that your first sentence. follow this by who, what, when, where, and how. use these, as necessary. example; (1) who (who needs it and or who does it), (2) what (specific description of what is needed), (3) when (specific, i need this by 8: 00 am monday or i need this by 10: 00 am today), (4) where (does it have to be printed and taken to someone, maybe the place of the meeting), (5) how (i need it scanned or faxed back to me at this email address, provide me with a hard copy).do not send yet. re-read it. did some spell check change a word? maybe let someone else read it for understanding. you want to avoid multiple emails asking for clarification. if important, put a read receipt on it. you will know it was opened, not necessarily read.end with a you.

Ithink the answer is both.