Path: utzoo!mnetor!uunet!lll-winken!csustan!polyslo!caus-dp!marcos
From: marcos@caus-dp.UUCP (Marcos R. Della)
Newsgroups: comp.lang.pascal
Subject: Code size problems
Message-ID: <337@caus-dp.UUCP>
Date: 21 Dec 87 16:27:14 GMT
Organization: USPFO for CA - Data Processing Div., SLO, Ca
Lines: 30
Keywords: overlays, too big, ugh!

I just got my copy of TP 4.0 about three weeks ago and have been busy
converting my BBS system from 3.0 to 4.0. Unfortunatly I ran into some
problems and after several calls to Borland, ran into a brick wall...

My original code contained 15 overlays that were converted into units.
These units were then optimized as all code was allowed in memory at once
and you didn't have to duplicate your efforts in several units. After
putting things all together I started getting "Out of Memory Error".

Boy oh boy was I disappointed. After talking to borland, I found out that
the system needed the entire program in memory to link the units together
and that there wasn't enough room in memory with the editor there. So they
recommended that I use the external compiler to put it together. Unfortunatly
that didn't work either so we tried to compile the system with the $L- set
off to get rid of the link buffer. Finally got the thing to compile with a
few bytes left over. I had no TSR's in memory and have 640k addressable. The
compiled code ended up around 251k in length.

I don't know about the units bit anymore. I like the idea and it makes things
really nice, but without overlays, there is NO method of handling a program
that starts getting a little large.

Any comments, suggestions, gripes, flames, etc. ;-)

Marcos Della

-- 
...!csustan ->!polyslo!caus-dp!marcos               | Whatever I said doesn't
...!sdsu ---/   Lt. Marcos R. Della                 | mean diddly as I forgot
...!csun --/    Smail:PO Box 8104 SLO,CA 93403-8104 | it even before finishing
...!dmsd -/     Tele: (805) 544-4900                | typing it all out!!! :-)