343ocs-0004ocs-0004.xmlNotes › Arena Allocator › Logic behind the allocatorOnly requires an offset or pointer to state the end of the last allocation. To allocate some memory from the arena it is as simple as moving the offset (or pointer) forward. The allocation has the complexity of . Due to being the simplest allocator possible, the arena allocator does nto allow the user to free certain blocks of memory. The memory is usually freed all at once.Context344ocs-0003ocs-0003.xmlNotes › Arena AllocatorNote2024529251ocs-0004ocs-0004.xmlLogic behind the allocatorOnly requires an offset or pointer to state the end of the last allocation. To allocate some memory from the arena it is as simple as moving the offset (or pointer) forward. The allocation has the complexity of . Due to being the simplest allocator possible, the arena allocator does nto allow the user to free certain blocks of memory. The memory is usually freed all at once.252ocs-0005ocs-0005.xmlBasic arena interfaceAn arena is like a stack with extensions, e.g. it can be named.the simplest arena allocator will look something likeWhile this is as simple as it gets, there are two issues with the basic approach * You cannot reuse this procedure for different arenas. * The pointer returned may not be aligned correctly for the data you need. The first issue can be solved by coupling the data into a structure and passing that to the procedure =arena_alloc=.