Carsten Haitzler (The Rasterman) wrote: > On Wed, 07 Sep 2005 07:06:06 +0200 Sebastian Dransfeld <[EMAIL PROTECTED]> > babbled: > > >>Carsten Haitzler (The Rasterman) wrote: >> >>>oh - you aRe right there - we only HAVE to malloc in the case of size == 32 >>>(ie to make sure the app gets 32bit data not 64bit data of whihc only >>>32bits is used...) BUT here's the catch: >>> >>>if you kjust pass back the data... how will the app free it? see the manual >>>page for XGetWindowProperty. you must use XFree on the data returns, but >>>since it may come from xlib direclty OR from us.. how do u know what free >>>to use. free () or XFree() ? :) sure - you can special case it "if the data >>>was 32bit use free otherise use xfree" but you need to track that now. i >>>did the "always make a copy" thing toi make it simple - we can always just >>>use free() and not worry :) >> >>What have you been smoking now? In ecore_x_window_prop_card32_set() you >>malloc, set the data, then free, so all actions is in this func. No problem. > > > we're talking about the get() not set() here :) > You are talking about get(). Of course I completely agree with you there. I think the rest of us have been talking about ecore_x_window_prop_card32_set(), which is the one rephorm fixed. I guess this is where the wires got crossed.
/Kim ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
