www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/04/14/23:48:38

Xref: news2.mv.net comp.os.msdos.djgpp:2701
From: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups: comp.os.msdos.djgpp
Subject: Transition from DJGPP1 to DJGPP 2.0
Date: 14 Apr 1996 07:43:41 GMT
Organization: The National Capital FreeNet
Lines: 24
Sender: ao950 AT freenet2 DOT carleton DOT ca (Paul Derbyshire)
Message-ID: <4kqabd$lo9@freenet-news.carleton.ca>
Reply-To: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host: freenet2.carleton.ca
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp



I have been wanting to upgrade to DJGPP 2.0 since most of the new tools
and that are for 2.0 only, but one thing is holding me back.

In DJGPP 2.0, the 0xD0000000 address for video memory was removed. This
will break virtually all my already written programs, requiring me to
rewrite all their video functions to use the slower libgr that routines,
and requiring me to completely rewrite programs that use a blitting
function I wrote.
Is there any way to upgrade and preserve backward compatibility for these
programs? (In fact it seems rather irresponsible, at least in hindsight,
to make a feature on a program only to remove it later such that people
have to rewrite lots of stuff... Was it known in advance when you made the
D0000000 thing that it wasn't permanent, as my docs never said not to use
it...?)
If there isn't, what the heck am I supposed to do to upgrade them?

--
    .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
 -()  <  circles, and bark is not smooth, nor does lightning travel in a
    `*'  straight line."    ,------------------------------------------------
         -- B. Mandelbrot  |  Paul Derbyshire (PGD) ao950 AT freenet DOT carleton DOT ca

- Raw text -


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