On 09/28/2014 08:58 PM, Lag Programming wrote:
@Nikolay
Thank you for your answer. :) Now that you've answered, can you
further respond to the following question: why is it needed to zero
fill the memory allocated that exceeds the requested value?
a) "pointer:=allocmem(initialsize);
realloc
@Nikolay
Thank you for your answer. :) Now that you've answered, can you further
respond to the following question: why is it needed to zero fill the memory
allocated that exceeds the requested value?
a) "pointer:=allocmem(initialsize); reallocmem(pointer,increasedsize);". I
don't see the ben
On 09/28/2014 05:45 PM, Lag Programming wrote:
Hi! I need some help in understanding three things viewed in heap.inc.
...
3) I'm not interested in the importance of the presented function. Why
the "existing" code design is preferred over "alternative" code?
Existing code:
function SysAlloc
Hi! I need some help in understanding three things viewed in heap.inc.
1) Why is variable "heap_lock_use" declared as "integer"? Apparently this
variable never gets a negative value. Also, this variable never gets used as a
parameter to a function/procedure call that would require a transform
