Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!rit!ritcv!ajy2208 From: ajy2208%ritcv@cs.rit.edu Newsgroups: comp.sys.atari.st Subject: Re: dissassembly Message-ID: <1540@cs.rit.edu> Date: 17 Jan 90 05:34:53 GMT References: <1534@cs.rit.edu> <10665@stag.math.lsa.umich.edu> 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 <10665@stag.math.lsa.umich.edu> hyc@math.lsa.umich.edu (Howard Chu) writes: [...informative stuff deleted...] > >As for the stray data at the top, perhaps you're not aligning the >screen memory correctly? This was a problem at first, as I am a beginning ST programmer and am not a registered developer (yet.. :-). Of course, the people who wrote the MWC documentation didn't bother mentioning the fact that the memory has to be ALIGNED.. But they provided a nice example, in which they aligned the memory, so that's how I learned.. >If you're writing code that you eventually hope for >other people to use, don't hard-code magic numbers like 32K into your >screen manipulation routines. [In fact, don't even use 32K. You only >need, at most, 32256, to get 32000 bytes on a 256 byte boundary, eh?] Kind of interesting, that the example in the MWC manual does have 32K hard wired in. Of course, it's only an example, but for someone learning how to do something for a first time, it's not setting a GOOD example.. sigh.. (at least it does have LOTS of examples).. Thanks! _____________________________________________________________________________ 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