Date:	Wed, 5 Feb 92 19:26:13 EST
From:	DJ Delorie <dj AT ctron DOT com>
To:	SORROW AT MAPLE DOT decnet
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Reasons not to use DJGPP :-)
Status:	O

Just to clear up a few things:

>Cons:

>1.  Uses G++, and thus is does not support cfront or ANSI C++.  It's pretty
>    close but there are noticeable differences.
Gcc 2.0 should be omre cfront compatible.

>3.  Does not support DPMI 1.0 ( does it now? )
*Windows* doesn't support DPMI 1.0.  Go32 will have DPMI 1.0 support as
soon as I get a server to test it against.

>Pros:

>3.  Supports VCPI, XMS, int15h, and DPMI 0.9.
DPMI 0.9 does not provide enough functionality to support go32.

>Some other problems may be that it is not MSC source compatible, etc.  I
>guess it depends on whether you are looking to port from UNIX to 386 or
>from DOS to 386.  It would probably be easier to port from UNIX, since
>DOS has too many picky little things about it to port to G++ effectively.

Yeah, the target audience is Unix programmers who are sick of porting
their 32-bit gcc sources to 16-bit DOS sources.

>I was wondering...is DJGPP going to support G++2.0 soon?  Also, is DJGPP
>going to be releasing a new version of DJGPP soon?

I'm hoping that nothing serious will happen requiring a 1.06 version,
as I'd like to concentrate on the 2.0 version of go32, which
(hopefully) will include multitasking, signals, pipes, etc.  The FSF
has my source diffs for MS-DOS, so gcc 2.0 is already ported to go32.
As soon as it's released I'll have a new cpp/cc1/cc1plus/gcc
available.

DJ
dj AT ctron DOT com
Life is a banana.

- Raw text -