Mail Archives: djgpp/1996/09/12/01:11:04
Xref: | news2.mv.net comp.os.msdos.djgpp:8524
|
From: | "John M. Aldrich" <fighteer AT cs DOT com>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Pointer variables
|
Date: | Wed, 11 Sep 1996 21:40:23 -0700
|
Organization: | Three pounds of chaos and a pinch of salt
|
Lines: | 26
|
Message-ID: | <32379437.2C7@cs.com>
|
References: | <517i6b$hqp AT news DOT ghgcorp DOT com>
|
NNTP-Posting-Host: | ppp211.cs.com
|
Mime-Version: | 1.0
|
To: | Rodney Bachtel <rbachtel AT mailman DOT ghgcorp DOT com>
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Rodney Bachtel wrote:
>
> Last question for a while, I promise. What is the C equiv. of the
> pascal pointer type? In pascal, it is a 32bit ptr, but I can't get DJGPP
> to do a int far *goober as is recommended for TurboC.
Turbo C is a 16-bit realmode compiler. DJGPP is a 32-bit DPMI compiler.
Thus it does not need far pointers and the 'far' keyword is obsolete.
As far as DJGPP is concerned, all your memory is in one humongous block
with a maximum size of 4 gigabytes; in other words, forget all about
segments, MK_FP, and all other 16-bit limitations. :)
If you are trying to use far pointers to access specific static memory
locations, such as video memory, you should read the DJGPP Frequently
Asked Questions list (v2/faq201b.zip), which tells you how to go about
this.
--
John M. Aldrich, aka Fighteer I <fighteer AT cs DOT com>
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d- s+:- a-->? c++>$ U@>++$ p>+ L>++ E>+ W++ N++ o+ K? w(---) O-
M-- V? PS+ PE Y+ PGP- t+(-) 5- X- R+ tv+() b+++ DI++ D++ G e(*)>++++
h!() !r !y+()
------END GEEK CODE BLOCK------
- Raw text -