Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version nyu B notes v1.5 12/10/84; site acf4.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!dcdwest!ittvax!decvax!genrad!mit-eddie!godot!harvard!seismo!cmcl2!acf4!cada
From: cada@acf4.UUCP (CADA (Ada/Ed in C) D. Shields)
Newsgroups: net.micro.pc
Subject: Re: Is it Lattice or me???
Message-ID: <1050007@acf4.UUCP>
Date: Sun, 27-Jan-85 22:20:00 EST
Article-I.D.: acf4.1050007
Posted: Sun Jan 27 22:20:00 1985
Date-Received: Sat, 2-Feb-85 11:08:51 EST
References: <1050005@acf4.UUCP>
Organization: New York University
Lines: 21

I don't think your problem is stack space because that is normally a run
time check.  Which memory model are you using ?  In all models the maximum
amount of statically allocated data is 64K (static data is put in the data
segment).  The maximum size of a single object is 32K.  Also if you are
using the small (default) model, the sum of the static data, stack and heap
cannot be more than 64K.  Try moving to the D model and see if it clears
up.  If that does not work then the only possible solution I can think of
(since it worked until you added a few variables) is to use the D or L
memory models and use the heap for your data.  For example to create an 256K
byte array of integers:

          int *d;
          char *getml();

          d = (int *) getml(256000L);

Using the large memory model, we created a program (the NYU ADA/Ed front end)
which had 160K of code and 130K of data. We were using version 2.00 of the
Lattice compiler.

                                                 Sam Chin