Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!samsung!aplcen!haven!udel!rochester!rit!ritcv!ajy2208 From: ajy2208%ritcv@cs.rit.edu Newsgroups: comp.sys.atari.st Subject: Re: dissassembly Message-ID: <1534@cs.rit.edu> Date: 15 Jan 90 21:39:10 GMT References: Sender: news@cs.rit.edu Reply-To: ajy2208%ritcv@cs.rit.edu (Albert Yarusso) Organization: Rochester Institute of Technology, Rochester, NY Lines: 28 In article V067MAJP@UBVMSC.CC.BUFFALO.EDU (Arion) writes: >It seems to me (IMHO) that if developers keep taking advantage of >"side-effects" and Atari tries it's best to keep programs from breaking, >eventually, you won't be able to revise TOS at all. > >I mean, if a program breaks because a programmer takes advantage of an >undocumented or illegal "feature" which isn't there at the next os revision, >isn't that the programmer's fault? Hmm, this reminds me of what happened when Atari brought out the XL operating system for the 8-bit computer.. A LOT of programs broke because programmers did not follow the rules... > John I have Mark Williams C, and am curious: What is the difference between malloc() and Malloc() ???? I am writing a slideshow/picture viewing program, and when I used malloc() to get a 32k block of memory for a picture, the picture always had some stray data at the top (looked suspiciously like the other variables I was using).. However, when I used Malloc() this disappeared. Boy, I almost pulled my hair out trying to figure out what was wrong!!! _____________________________________________________________________________ Albert Yarusso, Rochester ajy2208@ritvax.bitnet,ajy2208@ultb.isc.rit.edu Institute of Tech. _________________________________________________________ Computer Science /___ / {rutgers, ames}!rochester!ritcv!ajy2208 ______________________/ / ajy2208@ritcv.cs.rit.edu GEnie: A.Yarusso