Date: Sun, 08 Oct 2000 20:40:52 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: jt williams <jeffw AT darwin DOT sfbr DOT org>
Message-Id: <8361-Sun08Oct2000204052+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
CC: djgpp AT delorie DOT com
In-reply-to: <200010081611.LAA14033@darwin.sfbr.org> (message from jt williams
	on Sun, 8 Oct 2000 11:17:02 -0600)
Subject: Re: When is a DOS app a "32-bit DOS" app?
References:  <200010081611 DOT LAA14033 AT darwin DOT sfbr DOT org>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: jt williams <jeffw AT darwin DOT sfbr DOT org>
> Date: Sun,  8 Oct 2000 11:17:02 -0600
> 
> Strange question:  When is a DOS app a "32-bit" app?

When it uses 32-bit code.  It doesn't need to be a protected-mode app,
btw: Borland's 3.x compiler could produce 32-bit instructions without
going PM (but it couldn't use 32-bit pointers, of course).

> Suppose a certain application program 'foo.c' is written to compile using 
> 16-bit tools (e.g., Borland).  And suppose that by using '#ifdef __DJGPP__' 
> statements and DOS-specific DJGPP functions (e.g., _get_dos_version(), etc), 
> the code is also made to compile with DJGPP and to generate an executable that 
> works (with cwsdpmi).
> 
> Is 'foo.exe' now a 32-bit DOS app?

Once it's compiled with DJGPP, it's a 32-bit protected-mode
application.  Only the executable can be 32-bit or 16-bit, the source
is neither, it's just a text file.