[PULL libXdmcp] Cleanups: getting rid of X{alloc, free, realloc}, others
Mikhail Gusarov
dottedmag at dottedmag.net
Wed May 5 15:38:49 PDT 2010
Twas brillig at 15:23:58 05.05.2010 UTC-07 when jamey at minilop.net did gyre and gimble:
JS> I think it isn't safe to get rid of Xalloc and friends in client
JS> libraries. As I understand it, they're still relevant on Windows
JS> because of some kind of DLL crap. (XCB doesn't offer any of those
JS> wrappers and the Windows folks seem to have become resigned to that
JS> fact, but that doesn't mean we can break existing libraries.)
AFAIR it is only related to malloc/free usage which crosses
application/dll boundary. All memory operations in libXdmcp are
encapsulated, so it should not be a problem.
JS> It'd probably help if Windows folks could correct the, undoubtedly
JS> many, things wrong with what I've just written. :-)
Yes, I'd love to hear from them too: distant memories from the past and
blind googling are not the best sort of accurate information.
--
http://fossarchy.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100506/ea0dba74/attachment.pgp>
More information about the xorg-devel
mailing list