home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gumby!wupost!cheswicks!f0.n86.z86.toadnet.org!Peter.Garner
- From: Peter.Garner@f0.n86.z86.toadnet.org (Peter Garner)
- Sender: ufgate@cheswicks.toadnet.org (newsout1.26)
- Newsgroups: comp.os.ms-windows.programmer.tools
- Subject: Re: BC++ far* default in
- Message-ID: <53.2B02CF61@cheswicks.toadnet.org>
- Date: Wed, 11 Nov 92 11:50:00 cdt
- Organization: FidoNet node 86:86/0 - Zone Toad, St Louis MO
- Lines: 26
-
- JG> I am writing my first app, and I am using large model (BC++ JG>
- Does that [using the far keyword] give me 'another' 64k data
- JG> segment?
-
- Sort of. I don't know how the borland linker groups data, you may get
- a separate 64k segment for each module containing data declared as far,
- or you may get one far segment and one DGROUP. But yes, if you get the
- message 'DGROUP exceeds 64K" or something similiar, you need to declare
- data as far. Depending on your app and how you use memory, (All calls
- to malloc and calloc return memory allocated from outside of DGROUP) you
- may not run into the problem at all. Very few programs use more than
- 64K of static data. If you can allocate memory at runtime, you shouldn't
- have a problem.
-
- Good Luck
- Peter.
-
- * KWQ/2 1.0 *
-
-
- --- WM v2.04/92-0499
- * Origin: Cheswick's * HST/DS * STLMO (86:86/0)
- --
- Peter Garner - via Toadnet/UUCP Gateway 86:86/200
- UUCP: ....!wupost!0!Peter.Garner
- INTERNET: Peter.Garner@f0.n86.z86.toadnet.org
-