delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/10/05/06:34:04

From: Fokkema DOT DBRA AT delorie DOT com, 1043730 <dfokkema AT cs DOT vu DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: far pointers again
Date: Tue, 5 Oct 1999 08:44:55 GMT
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Lines: 18
Message-ID: <7tcdq7$7ug@cs.vu.nl>
NNTP-Posting-Host: galjas.cs.vu.nl
X-Newsreader: TIN [version 1.2 PL2]
X-Poster-Key: sha1:VUOYAQwNb4g3ZizE+gDoviyVHLk=
Cancel-Lock: sha1:LnVbh0j2mp5rE/HyhY83kA+zp3o=
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi all!

I wonder why djgpp doesn't have support for far pointers. As I understand,
gcc is ported from unix and it will work under various unix variants like
linux. I was told that under linux, one can create other descriptors in the
ldt and reference to them by using far pointers (of course). If this is all
true, I would say that gcc should support far pointers to easily reference
to these segments. Right now, I have to use temporary variables to store the
information when I decide to, say, use printf to display a number which is
stored in another segment. When I want to print a string part stored in
another segment I should design a printf which handles far pointers or copy
the string to the ds segment? I don't know exactly what to do, but it sure
generates a lot more inefficient code than any compiler which does support
far pointers.

Maybe I'm wrong on some points, so please correct me or post other comments.

David Fokkema

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019