delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/06/01/02:46:13

Date: Thu, 1 Jun 1995 08:25:37 +0300
From: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: dpmi DS:VRAM hack
Cc: Giva AT bbb DOT no

> Another solution to all these far-memory tricks (and hacks) would be
> real far-pointers. How difficult would it be to implement this in
> GCC ? This is a FSF issue I presume, but the djgpp community has lot
> of pull there.

What's wrong with the DJGPP farptr functions?  I find them much better
approach than the much-hated (at least by me) far pointers, because the
latter pollute the program source in a way which makes porting very
difficult.  Function call is much cleaner way: you just rewrite a single
function and roll.  And farptr functions compile to the same 2 machine
instructions which a compiler would emit for real far pointers, so
there's no runtime penalty, either.

But I guess there always be people who can't do without tricks and hacks...

- Raw text -


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