Date: Tue, 2 Nov 1999 09:55:40 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Gautier <Gautier DOT deMontmollin AT maths DOT unine DOT ch>
cc: djgpp AT delorie DOT com, "David C. Hoos, Sr." <david DOT c DOT hoos DOT sr AT ada95 DOT com>
Subject: Re: Using Micro$oft libraries in dgpp programs
In-Reply-To: <381DA675.A615188@maths.unine.ch>
Message-ID: <Pine.SUN.3.91.991102095529.19809D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 1 Nov 1999, Gautier wrote:

> Mmmh it mainly depends on 16 bit or 32 bit (DJGPP is furiously
> 32-bit). If you are using DJGPP GNAT/DOS and only have
> 16-bit sources/object files, you'll better have to translate
> into Ada (with inline assembler if needed to avoid makefile and so).

With all due respect to Ada (and its promoters ;-), I can hardly
believe it would be easier to convert a C program written for a 16-bit
compiler to Ada than to DJGPP.  If you really mean that, please
provide some examples to back up your opinion.

> On DJGPP the 16-bit stuff, e.g. calls to DOS, acess to conv. mem.,
> is passed through the DPMI interface with special calls.

Not entirely true.  Some calls can be left unchanged, because DJGPP
has the same functions (with different guts).  Examples include
int86, findfirst/findnext, conio functions, and lots more.