Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!MAPS.CS.CMU.EDU!Matthew.Diamond
From: Matthew.Diamond@MAPS.CS.CMU.EDU
Newsgroups: comp.windows.x
Subject: Re: Xt unportability (solved)
Message-ID: <9007162210.AA06896@ATHENA.MIT.EDU>
Date: 16 Jul 90 22:10:09 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 9


That was fast.  Turns out in R4 there is a switch to compile libX11
(MALLOC_0_RETURNS_NULL) for systems that return NULL when asked to allocate
0 bytes.  (All the switch does is add a check: if someone asks for 0 bytes,
the call to malloc will actually request 1 byte.)

Thanks for the quick responses.
Matthew Diamond
matt@maps.cs.cmu.edu