Article View: comp.os.ms-windows.programmer.misc
Article #1837Re: Segmented Memory Woes and Portability
From: John Grant
Date: Tue, 15 Dec 1992 17:48
Date: Tue, 15 Dec 1992 17:48
27 lines
1505 bytes
1505 bytes
In article <711@lax.lax.pe-nelson.com> twbrown@PE-Nelson.COM (Tom W. Brown) writes: >In article <wf=Fjj_00WB8QZoUYr@andrew.cmu.edu>, ak10+@andrew.cmu.edu (Andrew Joseph Kompanek) writes: [...stuff deleted about segmented memory confusion...] Here's Tom's answer: >Certainly it's possible to do that though I've tried to stay away from huge >pointers because; 1) of the overhead in their use, Yes, but it's really not that bad is it? 2) they chew up selectors, Tom, could you please explain this - I don't understand. >and 3) the "conventional" normalized huge pointers can't be used in >protected mode Windows programming. I don't understand this either. Are there 2 kinds of huge pointers? - "conventional" & "non-conventional"? And why can't they be used in protected mode? [...more stuff deleted...] I reposted this because I thought the questions and Tom's answers might be of general interest. -- John A. Grant jagrant@emr1.emr.ca Airborne Geophysics Geological Survey of Canada, Ottawa
Technical Details
Message-ID:
<1992Dec15.174802.15272@emr1.emr.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!torn!nott!emr1!jagrantReferences:
<wf=Fjj_00WB8QZoUYr@andrew.cmu.edu> <711@lax.lax.pe-nelson.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.ms-windows.programmer.misc Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!torn!nott!emr1!jagrant From: jagrant@emr1.emr.ca (John Grant) Subject: Re: Segmented Memory Woes and Portability Message-ID: <1992Dec15.174802.15272@emr1.emr.ca> Organization: Energy, Mines, and Resources, Ottawa References: <wf=Fjj_00WB8QZoUYr@andrew.cmu.edu> <711@lax.lax.pe-nelson.com> Date: Tue, 15 Dec 1992 17:48:02 GMT Lines: 27