Bug 899385 - Update comments that incorrectly state nsIPresShell::AllocateBlah are fallible. r=dbaron

This commit is contained in:
Cameron McCormack 2013-07-31 10:52:32 +10:00
parent 5ecbce73bd
commit 649b18b958

View File

@ -207,7 +207,7 @@ public:
* are also recycled using free lists. Separate free lists are
* maintained for each frame type (aID), which must always correspond
* to the same aSize value. AllocateFrame returns zero-filled memory.
* AllocateFrame is fallible, it returns nullptr on out-of-memory.
* AllocateFrame is infallible and will abort on out-of-memory.
*/
void* AllocateFrame(nsQueryFrame::FrameIID aID, size_t aSize)
{
@ -232,7 +232,7 @@ public:
* This is for allocating other types of objects (not frames). Separate free
* lists are maintained for each type (aID), which must always correspond to
* the same aSize value. AllocateByObjectID returns zero-filled memory.
* AllocateByObjectID is fallible, it returns nullptr on out-of-memory.
* AllocateByObjectID is infallible and will abort on out-of-memory.
*/
void* AllocateByObjectID(nsPresArena::ObjectID aID, size_t aSize)
{
@ -258,7 +258,7 @@ public:
* from a separate set of per-size free lists. Note that different types
* of objects that has the same size are allocated from the same list.
* AllocateMisc does *not* clear the memory that it returns.
* AllocateMisc is fallible, it returns nullptr on out-of-memory.
* AllocateMisc is infallible and will abort on out-of-memory.
*
* @deprecated use AllocateByObjectID/FreeByObjectID instead
*/