Xref: utzoo comp.sys.mac:44023 comp.sys.mac.programmer:11082 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!sun-barr!lll-winken!scooter!neoucom!sam From: sam@neoucom.UUCP (Scott A. Mason) Newsgroups: comp.sys.mac,comp.sys.mac.programmer Subject: Re: Novice Programmer Question: Dynamic Memory Allocation under TC Message-ID: <1856@neoucom.UUCP> Date: 11 Dec 89 22:10:36 GMT References: <24770@cup.portal.com> <4196@sbcs.sunysb.edu> Reply-To: sam@neoucom.UUCP (Scott A. Mason) Distribution: usa Organization: Northeastern Ohio Universities College of Medicine Lines: 14 Actually the fix may be very simple. I had a similiar problem when porting some code from an (yuck) MeSsy-DOS program. I finally found out that Think C happily lets me compile a program with (x)alloc calls in it without the library included, but does strange things with the pointers allocated. The moral of this story is: ALWAYS #include or similar include to make sure (x)alloc is used from the library. -- -------------------------------------------------------------------------------- "If it ain't broke, don't fix it," and certainly don't blame me. UUCP: {pitt,scooter,hal,cwjcc,aablue}!neoucom!sam INTERNET: sam@neoucom.EDU Scott A. Mason, Coordinator of Systems Operations, NEOUCOM