MB>
  >                                                  This is
  > not the same thing as saying that anything at all is being
  > "allocated."  Address space is a phantom quantity: it isn't
  > even uncommitted memory, but is unallocated memory.
MB>

  Actually, Mike, Mario is using the correct terminology.

  The CP reference uses the term "allocate" to refer to grabbing address
  space (by creating a memory object) and "commit" to refer to placing a
  page behind address space that has been allocated.

  And, frankly, I have to side with the CP reference here.  When I ask
  OS/2 for memory, it allocates a portion of my process' address space.  I
  then have to *further* ask OS/2 to assign backing storage for that
  address space, by "committing" a page to it, so that I can legally refer
  to that storage in my program.

  Address space is a very real quantity, and it is important to remember
  that on OS/2 the concept of allocated address space is a valid one, and
  one that is different from the concept of actual physical pages of
  memory used.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 3.01