Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!zehntel!dual!amd70!decwrl!decvax!ucbvax!ucbcad!tektronix!hplabs!sri-unix!pam@Purdue.ARPA
From: pam@Purdue.ARPA
Newsgroups: net.micro.pc
Subject: Lattice C #include files
Message-ID: <1237@sri-arpa.UUCP>
Date: Fri, 22-Jun-84 09:56:00 EDT
Article-I.D.: sri-arpa.1237
Posted: Fri Jun 22 09:56:00 1984
Date-Received: Thu, 28-Jun-84 06:27:08 EDT
Lines: 17

From:  Paul McNabb <pam@Purdue.ARPA>

After several hours of frustration I have found an interesting
"feature" of the Lattice C compiler.  I am running an IBM-PC with
640K with an AST board and associated software.  It seems that
if I have <128K of memory for user programs, the first pass
of the compiler reports that it cannot find any of my header
files; a very unnerving error to get.  When I increase the memory
slightly I can get it to "find" only include files that aren't 
nested.  It seems that the more 64K segments I have available the
greater the amount of #include nesting I can use.  Can I assume
that these guys are reserving full segments for each level of
header files?  Anyone else seen this behavior?

Paul McNabb
Purdue University
(pam@purdue)