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: <54.2B02CF63@cheswicks.toadnet.org>
- Date: Wed, 11 Nov 92 16:26:19 cdt
- Organization: FidoNet node 86:86/0 - Zone Toad, St Louis MO
- Lines: 47
-
- PP> In your data declarations, if you do not specifically specify PP>
- keyword far, then the declaration is left in the default data
-
-
- Aha, so you think that what that guy wanted was a way to get his medium
-
- model data out of DGROUP. I hvae run into that problem, even in the
- large model. MSC has a compiler line switch to automatically move all
- string constants out of DGROUP, if this is compiled:
-
- double lfAngle; // 8 bytes taken up in DGROUP
- char far caPrompt[8]; // 8 bytes stored in a far segment NOT
- // in DGROUP
-
- Unfortunately, I know of know way to accomplish this with BC++. In
- fact, I participated in the writing of a large model C++ multimedia GUI
-
- authoring package for Chrysler last year, and we never did figure out
- how
- to DEFAULT data out of DGROUP. As you said, you can EXPLICITLY declare
-
- the data as far, but there seems to be no way to make that a default.
- Also in the medium model all your medium model library fcns will crash
- when they attempt access data in another segment witha near pointer!
- Now
- that you have pointed out what this guy really wants (he DID ask a very
-
- good question) I am most interested in the answer.
-
- Thank you
-
- Peter
-
-
- * KWQ/2 1.0 *
-
- .
-
- * 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
-