Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: image memory deallocation
Message-ID: <9005081418.AA01220@expire.lcs.mit.edu>
Date: 8 May 90 14:18:10 GMT
References: <55815@bbn.BBN.COM>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 7


    Does [XDestroyImage] really deallocate the image memory?

Yes, I'm afraid it does.  [Several Xlib image routines are pretty broken.]
You either have to null out this field before you destroy, or else after
you create you can replace the destroy_image function in the image object
with one of your own choosing.