Linked List w/o "new" ?

[LouB]

I have a program where I have an array of memory called hypomem[10000]. I have implemented a cpu simulator which loads a program into hypomem, then executes the program (which is written in machine language) by doing operations such as add, subtract, etc. I am now writing simulator functions for an operating system so I can load more than one program and have a scheduler run the programs according to priority. What i need to do is use linked lists to allocate portions of the hypomem for different things. I cannot use the "new" since that will not allocate it in the hypomem, it will allocate it in the machines main memory. Does anyone know how I would go about this? Are there any programs out there that someone can post that will show me how this works? Any help is appreciated.

[jverkoey]

wow, that's taking virtual computer to a whole new level what i'd suggest is making your own function that will return a "pointer" to a spot in your hypomem. for example:

unsigned int createHypoDat(unsigned int size)
{
	do some stuff to find the next closest empty "block" of hypomem
	return <index to the beginning of the block>
}

That seems like the best way to do it to me, i'm not sure how you'd efficiently make sure that you weren't writing over other blocks and things, but that's a good place to start i guess

[Hunter2]

Why do you need to use the static array anyways? Can't you dyamically allocate one (or more) based on how much memory you need?

If you still want to allocate hypomem... basically what allocation is (from what I know) is giving you a pointer to the section of memory, and marking that area off as "reserved" so that nothing else will modify the data. You could try setting up a linked list or vector of 'fenced-off' areas or something, and add to it when you 'new' and delete from it when you 'delete'. I haven't tried anything like this before, but that's all I can think of.

[LouB]

Thanks guys. I'm going to give jverkoey's suggestion a try. It seems to make sense if I can get it to work!!

[jverkoey]

probably a mergence of mine and hunter2's suggestion would be a good thing to do, as hunter2's would make sure that you aren't returning a pointer to a block of memory that overlaps another one's memory

[Magos]

If the memory allocated is a class, you could overload the new operator and manually take memory from that array.