Compare Revisions

Choosing the right memory allocator

Change Revisions

Revision 121745:

Revision 121745 by Mook on

Revision 121746:

Revision 121746 by QdtA3d on

Title:
Choosing the right memory allocator
Choosing the right memory allocator
Slug:
Choosing_the_right_memory_allocator
Choosing_the_right_memory_allocator
Tags:
Add-ons, XPCOM, Plugins, NSPR, "Developing Mozilla"
Add-ons, XPCOM, Plugins, NSPR, "Developing Mozilla"
Content:

Revision 121745
Revision 121746
t141      Because C++ objects that implement XPCOM interface types det141      Because C objects that implement XPCOM interface types dele
>lete themselves when the final <code>Release()</code> is called, >te themselves when the final <code>Release()</code> is called, th
>they can be safely allocated using the native <code>new</code> an>ey can be safely allocated using the native <code>new</code> and 
>d <code>delete</code> operators. The <code><a href="en/NS_NEWXPCO><code>delete</code> operators. The <code><a href="en/NS_NEWXPCOM"
>M">NS_NEWXPCOM</a></code> and <code><a href="en/NS_DELETEXPCOM">N>>NS_NEWXPCOM</a></code> and <code><a href="en/NS_DELETEXPCOM">NS_
>S_DELETEXPCOM</a></code> macro wrappers are entirely unnecessary >DELETEXPCOM</a></code> macro wrappers are entirely unnecessary an
>and make code harder to read.>d make code harder to read.

Back to History