home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!munnari.oz.au!metro!usage!news
- From: troy@cbme.unsw.EDU.AU (Troy Rollo)
- Subject: Re: Automatic data segment exceeds 64K
- Message-ID: <1993Jan10.010634.13926@usage.csd.unsw.OZ.AU>
- Sender: news@usage.csd.unsw.OZ.AU
- Nntp-Posting-Host: plod.cbme.unsw.edu.au
- Organization: University of New South Wales
- References: <2935516401.1.p00090@mail.psi.net>
- Date: Sun, 10 Jan 1993 01:06:34 GMT
- Lines: 20
-
- From article <2935516401.1.p00090@mail.psi.net>, by "Jeffrey P. Overcash" <p00090@mail.psi.net>:
- > seems to be affecting this problem. The manual says to use the map file
- > to determine the sizes of the componant segments to see which modules
- > contribute what to the DGROUP. I've done this but nowhere can I find
- > out how to move a module into another segment. Any and all help will be
- > greatly appriciated.
-
- To do this, you will need to find the global and static data in the modules
- contributing most to the DGROUP segment, and move that data into separate
- modules. This data should then be compiled in the *HUGE* memory model.
- This data can then be declared external in the code modules. Using this
- technique of compiling code in the large model, and static data in the huge
- model, you effectively get to use the BC++ huge model for Windows programs.
- Note that string literals are also static data, and in extreme cases these
- may also need to be taken out and put into huge model modules.
- --
- _______________________________________________________________________________
- troy@cbme.unsw.EDU.AU Overworked, overcommited and always multitasking.
- Opinions expressed are not those of the CBME or UNSW, but are my opinions only.
- You are free to adopt them. I suggest you adopt them. You will adopt them!
-