const std::string SOME_STRING =

[andrewFl]

If this question is already ask please forgive me and let me know where it is.

1) which way is better? SOME_STRING is never modified.
2) Does C++ instantiate string object if I use the first method (const std::string SOME_STRING = "This is a test.")
3) If I use the second method, do I need to destroy the object after I use it.
4) The first method, SOME_STRING will be placed in a heap or a stack?
5) I always use the first method, but some engineers told me that the second method is much better.

I really appreciate your help.

[weaknessforcats]

This code:

const std::string SOME_STRING = "This is a test.";
 
 

does create a string object. The object is created on the stack because it was not created using the new operator.

The code is really a constructor call:

const std::string SOME_STRING("This is a test.");

If you create your string using the new operator, then you must delete the object when you are finished with it.

Objects on the stack are managed by the compiler and they will be created and deleted by the compiler without telling you.

Objects on the heap are not deleted until you call the delete operator. These objects will exist until you are finished with them.

The engineers who favor the heap method are correct. You just need to remember to delete these objects to avoid memory leaks. Personally, I use stack variables only for local variables inside the function that I wanted deleted when the function completes.

You can even have your heap objects automatically deleted by using a smart or managed pointer. Read this: http://bytes.com/topic/c/insights/65...-smart-pointer

[andrewFl]

thanks so much for your answer.