Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!ig!uwmcsd1!lakesys!jason From: jason@lakesys.UUCP (Jason) Newsgroups: comp.sys.atari.st Subject: Re: MWC & large arrays -- help! Summary: No, not very new to it... Message-ID: <782@lakesys.UUCP> Date: 28 Jun 88 07:45:13 GMT References: <734@cacilj.UUCP> <46700008@hcx2> <411@brambo.UUCP> <767@lakesys.UUCP> <2921@tekig5.TEK.COM> Organization: Lake Systems, Milwaukee Wisconsin Lines: 31 In article <2921@tekig5.TEK.COM>, wayneck@tekig5.TEK.COM (Wayne Knapp) writes: > In article <767@lakesys.UUCP>, jason@lakesys.UUCP (Jason) writes: > > > > Just for kicks and giggles, why would anyone want elements/structures > > that were >32k? Or, put differently, what's in it? Huge arrays? (Or 16384 > > ints? :) > > You must be joking, or maybe your are just new to programming. Yes the Nope, not joking. > [...] > Anyway here is a few that can require more than 32K access in arrays: > [Stuff listed] > Almost any type program can benefit from the "EASY" access of memory. When > one has a high level compiler why should he have to worry about array sizes > as long as there is enough real memory. > > Wayne Knapp Nope, being doing it for a little while... (Primarily on micros, which affects ones mindset regarding memory). But, I don't see why anything mentioned would have to have >32K ELEMENTS. One could easily enough (and, possibly, more conveniently, depending on how one was handling one's memory allocation) have a pointer to an array imbedded in a structure. I suppose my not being able to see why is pretty much irrelevant, as if someone wants to do something, they should be able to... "High level compiler"? C, the most popular bloated macro assembler? :) Jason - Not your average iconoclast.