Date:	Fri, 12 Feb 1999 13:33:27 -0500
Message-Id:	<199902121833.NAA20598@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	eplmst AT lu DOT erisoft DOT se
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<199902121828.TAA27210@juno.erisoft.se> (eplmst@lu.erisoft.se)
Subject:	Re: Carry flag
References:	<199902121828 DOT TAA27210 AT juno DOT erisoft DOT se>
Reply-To:	djgpp-workers AT delorie DOT com

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

That's the most commonly used flag, so yes.

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

I think we shouldn't add those definitions *twice*.  We've gone many
years without them at all, too.

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

A whole new file just to define some flags?  I'd rather find a good
place for them to live in an existing file.

Unless, of course, you want to create a <cpu.h> that has bitfield and
structure definitions for *all* the cpu registers (flags, tss,
descriptor tables, fpu, etc).

> Does Borland have these #defines? In what file?

No.  They assume you know what the flags register looks like.

- Raw text -