Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.sys.apple
Subject: Re: large GS programs in APW C
Message-ID: <9895@smoke.BRL.MIL>
Date: 22 Mar 89 03:59:01 GMT
References: <8903201806.aa11426@SMOKE.BRL.MIL>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 16

In article <8903201806.aa11426@SMOKE.BRL.MIL> AWCTTYPA@UIAMVS.BITNET ("David A. Lyons") writes:
>The 64K limit applies only to SIMPLE STATIC variables, right?  (Not
>to arrays or to auto variables.)  I have a hard time imagining how
>to use up all 64K.

I think earlier (Beta test) versions of APW C had a 64K restriction on
all data, not just nonaggregates.  APW C 1.0 (final version) does claim
to support large arrays.

I think autos are allocated off the "stack", which even with various
forms of kludgery (2/CSTART replacement) cannot exceed 64Kbytes.
Many so-called "real" computers like Gould PowerNodes have a similar
problem.  When designing code that might be used in such a small-stack
environment, it is important to assign larger objects to static storage
duration (in which case APW C and some IBM PC compilers may still have
problems) or to dynamically allocate them