Shulou(Shulou.com)06/01 Report--

This article mainly explains "Why C++ scope objects should not be built on heap memory". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's ideas slowly and deeply. Let's study and learn why C++ scope objects should not be built on heap memory.

R.5: scope objects should not be built on heap memory

Reason (reason)

Scope objects can be local objects, global objects, or members. This means that there is no additional allocation and release cost that contains the scope of the object or the object. Members of scope objects are scopes themselves, and their constructors and destructors manage the lifecycle of the object.

Example (sample)

The following example is inefficient (because it contains unwanted allocation and release actions) and is easy to throw an exception from. A memory leak will occur if partially returned, and it is lengthy.

Void f (int n)

{

Auto p = new Gadget {n}

/ /...

Delete p

}

Instead, use local variables:

Void f (int n)

{

Gadget g {n}

/ /...

} Enforcement (implementation recommendations)

(medium) alarm if an object is released on all paths after it is allocated within the same function. It is recommended that you use objects on the local automatic stack.

(simple) alarm if the local unique pointer or shared pointer is not moved, copied, reassigned or reset before the end of the life cycle.

Thank you for your reading. The above is the content of "Why C++ scope objects should not be built on heap memory". After the study of this article, I believe you have a deeper understanding of why C++ scope objects should not be built on heap memory, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.