From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Message-Id: <199902121828.TAA27210@juno.erisoft.se>
Subject: Re: Carry flag
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Fri, 12 Feb 1999 19:28:38 +0100 (MET)
Cc: dj AT delorie DOT com
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

DJ said:
> Users who need it would be using the dpmi.h or dos.h header anyway.
> machine/asm.h is for people writing .s files.  I think one option that
> wouldn't be too bad is to add these lines to both dpmi.h and dos.h:
> 
> #ifndef _CPU_FLAG_CARRY
> #define _CPU_FLAG_CARRY 1
> #endif
> 
> We can then debate a separate file that defines all the flag bits as
> _CPU_FLAG_* but dpmi.h and dos.h wouldn't need to include it.

I'm not sure I follow you. Are you saying that _only_ those _three_
lines should be added to dpmi.h (and dos.h)?

If so, then I don't understand why we shouldn't add the whole bunch of
them (parity, zero, sign, ...).

Personally I think the asm.h (not machine/asm.h) is the right way. Why
shouldn't dpmi.h include that file?

Does Borland have these #defines? In what file?


Right,

							MartinS