Allocation from "static array"

Hi all,
let's say we have a fixed array:

Code:

---

char pool[10000];

---

And now we want to "allocate" (not using "malloc", just take the addresses from this static array) e.g. 5 bytes and save them in some "char*", so that after the allocation:

Code:

---

char* newArray;

            .
            .  // Do that allocation (but how?)
            .

newArray[0] = 'a';  // Can be. Allocated address: "&pool[0]"
newArray[1] = 'b';  // Can be. Allocated address: "&pool[1]"
newArray[2] = 'c';  // Can be. Allocated address: "&pool[2]"
newArray[3] = 'd';  // Can be. Allocated address: "&pool[3]"
newArray[4] = 'e';  // Can be. Allocated address: "&pool[4]"
// newArray[5] = 'x';  CAN'T BE, we have allocated just 5 bytes

---

So does anybody know how to do that allocation to solve my problem?

Thanks.

You're going to need to keep track of "objects" within the pool. For example how much you've allocated, and the "start" address within the pool.

Code:

---

struct poolObject_s
{
    void * ptr;
    size_t size;
};

---

Then when you have to allocate, you find the first (or otherwise if you have a more advanced algo') free contiguous space that's large enough. Perhaps some sort of table would do well here :)

Problem? You haven't shown that simply using malloc is a problem. Care to elaborate on that?
If you are going to use some kind of pool allocator, then what you use or how it works is entirely dependent on how flexible it needs to be. E.g. Will everything allocated from it be of the same size or type? Does it need to be threadsafe? etc...
There's almost certainly no need to write it yourself. There are pre-made ones out there.

I think what Petike is charged to do is to create an alternative implementation of malloc.

It is not too hard to do - you need to implement some way to add the memory back when freeing, and to be able to find the first free block that is suitable size.

--
Mats

I don't see how the static array though will be connected with dynamically allocating memory from the heap.
Do you actually want to do your own malloc() or more a "virtual" malloc(), thus statically allocating int pool[] and then when your call your virtual_mallo() to be able to make some space valid to read/write?

Quote:

---

Originally Posted by C_ntua

I don't see how the static array though will be connected with dynamically allocating memory from the heap.
Do you actually want to do your own malloc() or more a "virtual" malloc(), thus statically allocating int pool[] and then when your call your virtual_mallo() to be able to make some space valid to read/write?

---

Yes, I think the original post wants to use the array as a heap.

--
Mats

Thank you all very much for your answers.