Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!m.cs.uiuc.edu!s.cs.uiuc.edu!carroll
From: carroll@s.cs.uiuc.edu
Newsgroups: comp.windows.x
Subject: Re: Free data from XGetWindowProperty
Message-ID: <216500009@s.cs.uiuc.edu>
Date: 18 Jun 89 17:00:00 GMT
References: <3174@ncsuvx.ncsu.edu>
Lines: 21
Nf-ID: #R:ncsuvx.ncsu.edu:3174:s.cs.uiuc.edu:216500009:000:1140
Nf-From: s.cs.uiuc.edu!carroll    Jun 18 12:00:00 1989


In article <3174@ncsuvx.ncsu.edu>, rcb@cccvs1.ncsu.edu (Randy Buckland) writes:
> In the XGetWindowProperty call, you get back a pointer to the property data.
> Should this be freed or not. I can't find anything in the documentation
> that goes either way.

[ ... answer about Xfree ... ]

Should you Xfree() if the XGetWindowProperty() calls returns a non-Success
value? Also, on a related topic, XLoadQueryFont() returns a structure that
should be freed. Can I use XFree on it? The manual (11.3) says to use
XFreeFontInfo(), but that wants a list of names as it's first argument -
where do I get that? And what possible purpose is there in passing them?
The names are supposed to be a list returned by XListFontsWithInfo(),
but the name (singular) that I have was generated elsewhere - if it gets freed,
things will break in a bad way. Should I pass a NULL pointer for the names
in XFreeFontInfo(), or just use XFree()? Thanks!

Alan M. Carroll                "And there you are
carroll@s.cs.uiuc.edu           Saying 'We have the Moon, so now the Stars...'"
CS Grad / U of Ill @ Urbana    ...{ucbvax,pur-ee,convex}!s.cs.uiuc.edu!carroll