🚀 go-pugleaf

Kazimir Kylheku (c2a192@ugrad.cs.ubc.ca) wrote:
: In article <nevin-2309950419270001@mac-nevin.cs.arizona.edu>,
: Nevin ":-]" Liber <nevin@CS.Arizona.EDU> wrote:

: >No.  Unlike you, they had practical problems to solve.  You stating that
: >it wasn't a problem doesn't make it so.  You *still* haven't posted a
: >solution to what to do if the heap is so fragmented that you can't satisfy
: >an allocation request, other than quitting the app or buying more
: >hardware.

: You can block the process until the request can be satisfied. You can
: raise some sort of exception and let the process handle it in whatever
: way it wants (including the option to try to restart the request).

And this is going to work really well on a single-tasking system... What 
if the process itself is what has (through normal usage) fragmented the 
memory? Block it until the cows come home?

: In any case, you have saved space by not bloating your code with silly
: wrappers around an overzealous global heap management scheme.

You still haven't explained what you'd have the OS do if all the memory 
was available to meet the request, but was fragmented... Just sit there 
and wait, or should you let the process move its own data around system 
memory? Nah, let the OS do it in a reliable and documented way.