From:	George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp and compatbilty with turbo c and other compliers
Date:	28 Nov 1997 06:03:10 GMT
Organization:	Oxford University, England
Lines:	30
Message-ID:	<65lmqu$d8b$2@news.ox.ac.uk>
References:	<65l85u$ni1$1 AT winter DOT news DOT erols DOT com>
NNTP-Posting-Host:	sable.ox.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On 28 Nov 1997 01:53:02 GMT in comp.os.msdos.djgpp kifox <kifox AT hotmail DOT com> wrote:

: How compatable is DJGPP with C code writen using Turbo C and other 
: compliers? 

: What I mean is how hard would it be to port programs written using these 
: compliers over to DJGPP?

How long is a piece of string? :)

It depends on a very large extent what the code you're using is like.
If it's ANSI-compliant, well-written, portable code, the porting
should be fairly trivial.  However, I don't think anybody ever wrote
portable code on Turbo C... ;)

If it uses many non-standard features, especially if it uses graphics
or other low-level hardware-specific devices, the porting will be more
work.

For detailed information on what sorts of things will be awkward to
port and how to go about adapting certain things to work in a DPMI
environment, I suggest you look at the FAQ section 17 and particularly
section 18.  If your code uses Borland's BGI graphics interface, you
can get djgpp's grx graphics library and the bcc2grx package, which
should help you in porting it to djgpp.  Or you could get Allegro,
which I personally prefer, but you'll need to change all the graphics
commands.  Allegro has support for other low-level devices too.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -