Mail Archives: djgpp/1997/01/03/16:30:39
From: | you AT somehost DOT somedomain (Your Name Here)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Memory management in DJGPP
|
Date: | 3 Jan 1997 19:39:46 GMT
|
Organization: | Your Organization
|
Lines: | 28
|
Message-ID: | <5ajna2$rqi@pulp.ucs.ualberta.ca>
|
References: | <5ahrj3$crt$1 AT news DOT utdallas DOT edu>
|
NNTP-Posting-Host: | violet.slis.ualberta.ca
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
In article <5ahrj3$crt$1 AT news DOT utdallas DOT edu>, rbrooks AT utdallas DOT edu says...
>
>I have a few questions about djgpp... since I am learning C++ from a
>different C++ book, there is some difficulty...
>
>First of all, gcc doesn't seem to handle the keyword far, as in:
>char far *harf;
Because DJGPP uses DPMI, it doesn't distinguish between near and far memory
blocks, and so it doesn't recognize the far keyword (because it's
unnecessary). (at least I think that's it... if I'm wrong, I hope some guru
will tell me)
>This was mentioned in the info libc.a help files... How can I maintain a
>similar functionality?
Again, I don't think you need to bother.
>Secondly, if I want to pass a memory value to a pointer, how do I go about
>doing this? (Both for far pointers and near pointer) I get a warning
>about casting harf (see above) to an int without a cast if I try something
>like:
>
>char *harf = 0x0013 or something similar.
Hmmm... are you trying to get *harf to point to addy 0x0013, or are you trying
to assign 0x0013 to whatever *harf is pointing at?
- Raw text -