Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!agate!ig!uwmcsd1!lakesys!jason From: jason@lakesys.UUCP (Jason) Newsgroups: comp.sys.atari.st Subject: Re: MWC & large arrays -- help! Summary: Uh, I think you misread something... Message-ID: <767@lakesys.UUCP> Date: 24 Jun 88 05:21:48 GMT References: <734@cacilj.UUCP> <46700008@hcx2> <411@brambo.UUCP> Organization: Lake Systems, Milwaukee Wisconsin Lines: 20 In article <411@brambo.UUCP>, sid@brambo.UUCP (Sid Van den Heede) writes: > In article <46700008@hcx2> jgj@hcx2.SSD.HARRIS.COM writes: > >I have experienced this problem too. As far as I can tell, in 3.0, structures > >are limited to 32Kb. Also, elements of an array are limited to 32Kb. > > I thought 3.0 was supposed to fix the problem with big arrays etc. > [Rest of article deleted] > Sid Van den Heede Voice: 416-792-1137 Version 3.0 does handle ARRAYS that are larger than 32k... I've never had any array ELEMENTS that've exceeded 32k (or any structures by themselves which were that big) so I can't verify/deny what was said about that. However, I DO know that MWC 3.0 properly handles large arrays (how large, I'm not sure) 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? :) Jason - Not your average iconoclast. "The first office copiers were, as is well known, monks." - David Owen