Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!adm!lhc!usenet
From: usenet@nlm.nih.gov (usenet news poster)
Newsgroups: comp.sys.mac.programmer
Subject: malloc() in Think C programming on the Mac
Message-ID: <1991Jan24.060336.12684@nlm.nih.gov>
Date: 24 Jan 91 06:03:36 GMT
Reply-To: werner@bio.NLM.NIH.GOV (Craig Werner)
Distribution: comp
Organization: National Library of Medicine, Bethesda, Md.
Lines: 9


	Is there an idiosyncracy about malloc() in THink C on the Mac.
Is there an idiosyncracy about this on the Mac.

I have code that compiles and runs under Unix and MSDOS.  On the Mac,
it compiles without error and runs most of the time, however calls
to malloc(() which on the other operating systems return a pointer
and space reture null on the Macintosh (using the Think C console.h
and ANSI libraries).