Date: Wed, 02 Mar 94 12:18:10 GMT
From: "Wayne G. Sullivan" <WSULIVAN AT IRLEARN DOT UCD DOT IE>
Subject: Big Arrays
To: djgpp AT sun DOT soe DOT clarkson DOT edu

That go32 can use virtual memory for large arrays is very useful, but in
my experience it does not always work as desired. With an earlier version
of djgpp, if an array was specified in the c-file to require more than
16MB, when the compilation came to the ld stage, there was much gnashing
of disk and eventually ld expired. With dj111m3, I can now have arrays
which require more than 16MB, but there is still much gnashing of disk
and when I ran chkdsk after the compilation, a chk0001 file of about 12MB
resulted. I have found that go32/djgpp quite often leaves fragments that
chkdsk has to clean up. Most often this occurs when a program is interrupted,
but it can occur at other times as well. I think djgpp is great, but I
recommend the frequent use of chkdsk/scandisk.
Wayne Sullivan