RM 13 11 23-25 Implicit Heap Usage (GNAT Reference Manual)

Next: RM 13.11.2(17): Unchecked Deallocation, Previous: RM 13.9(14-17): Unchecked Conversion, Up: Implementation Advice [Contents][Index]

6.30 RM 13.11(23-25): Implicit Heap Usage ¶

"An implementation should document any cases in which it dynamically allocates heap storage for a purpose other than the evaluation of an allocator."

Followed, the only other points at which heap storage is dynamically allocated are as follows:

At initial elaboration time, to allocate dynamically sized global objects.
To allocate space for a task when a task is created.
To extend the secondary stack dynamically when needed. The secondary stack is used for returning variable length results.

"A default (implementation-provided) storage pool for an access-to-constant type should not have overhead to support deallocation of individual objects."

Followed.

"A storage pool for an anonymous access type should be created at the point of an allocator for the type, and be reclaimed when the designated object becomes inaccessible."

Followed.