Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!shelby!labrea!daemon
From: combs@sumex-aim.stanford.edu (Dave Combs)
Newsgroups: comp.sys.next
Subject: Re: Objective C compiler options
Message-ID: <24047@labrea.Stanford.EDU>
Date: 31 Aug 89 18:22:54 GMT
Sender: daemon@labrea.Stanford.EDU
Lines: 20

Ali,
Thanks for your message.  It turns out the problem was a misunderstanding
I had about how the Storage class works.  In trying to follow the 
documentation, I was calling "free" on some items I had put into a Storage
instance, in the mistaken belief that what Storage was doing was to
allocate storage for managing pointers to items that I created (much as
the List class does).  It turns out, however, that Storage is actually
COPYING my data into storage it allocates for itself (which is obvious,
given the request for the item sizes when creating Storage, but I of
course missed this).  When the docs talk about "freeing" items from Storage,
I believe that they really mean "do any processing you need to do before
the pointer to the item is lost forever", rather than "free the storage
that I'm using to hold your data".
Anyway, when I realized this, I ceased trying to free pointers in the
Storage object, and everything worked fine.
Thanks again,
Dave  (combs@sumex-aim.stanford.edu)

P.S. Maybe somebody should expand the documentation on Storage just a bit,
to make the above points a bit more clear?  Just a suggestion.