Quiz submission record for quiz2-1-1 at Mon Jun 28 00:38:34 2004:

Your Answer for Question 1:
A. A sucessfull call to malloc will always decrease the number of free blocks. This is because malloc will leave the number of blocks unchanged if there is not room for the called memory or will return a NULL pointer if there is no room.










Your Answer for Question 2:
B: A call to free() may leave the number of free blocks in tact, because free releases blocks, even those not in used. If a part of memory is not being used and you free it, you still free some memory block. The same is true if you free a piece of memory you are using. If you free a block of memory that is being used you leave the free memory in tact. 

Your Answer for Question 3:
The Java equivalent to malloc is the new key word. The equivalent to free is not using the object as Java has garbage colllection. In Java, a variable not being used is garbage collected. C allows the programmer to manage memory.

Your Answer for Question 4:
No, because if the initial pointer gets changed you cannot reclaim where it once pointed to.

Your Answer for Question 5:
I still find malloc() confusing. I am still not sure when I need to use it.


Your unique submission ID is quiz2-1-1-cs61c-ap-1088408314-499.