Posts: 357
Threads: 118
Joined: Oct 2004
I'm sure that I'm just using it wrong:
Code:
Sub DestroyLinkedList(l as LinkedList)
dim p as ListElement ptr
dim c as ListElement ptr
p = l.Head
do while( p <> 0)
c = p
p = p->enext
deallocate c 'remove list element
loop
deallocate @l 'remove last traces of list
End Sub
When I call my PrintLinkedList sub, it shows that nothing was removed.
f you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows.
Posts: 108
Threads: 0
Joined: Jan 2006
This doesn't mean that your memory has not been deallocated. All your pointers still point to the same places in memory, and nothing has been overwritten yet. Deallocating memory alerts your memory manager that it can use that memory in a future memory allocation.
Posts: 306
Threads: 14
Joined: Nov 2002
You can always set the pointers to NULL after deallocating as well. It's what I do, though I'm not sure that it's necessary. :wink:
Posts: 357
Threads: 118
Joined: Oct 2004
Oh, so it is working. Thanks.
f you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows.
Posts: 3,522
Threads: 189
Joined: Dec 2003
Quote:You can always set the pointers to NULL after deallocating as well. It's what I do, though I'm not sure that it's necessary. :wink:
It's good practice, and helps avoid nasty bugs where you pass "dead" pointers.. If it's set to 0 most routines simply ignore it..
