X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Sat, 19 May 2012 14:13:56 -0400
Message-Id: <201205191813.q4JIDulU002792@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <jp839g$unq$1@speranza.aioe.org> (do_not_have@notemailntt.cmm)
Subject: Re: incompatible
References: <442a0 DOT 580acc3b DOT 3ce7635b AT aol DOT com> <83txzdstc1 DOT fsf AT gnu DOT org> <8c35d644-ede1-4b87-8c60-ebf6a0db0513 AT hq4g2000vbb DOT googlegroups DOT com> <jp6uks$g27$1 AT speranza DOT aioe DOT org> <f2041f3a-3eb3-4fbe-afc1-c4245314b211 AT r3g2000yqh DOT googlegroups DOT com> <jp839g$unq$1 AT speranza DOT aioe DOT org>
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


> I was glossing over it ...  DJGPP needs a purpose.

To me, DJGPP was never the goal.  DJGPP existed to *fulfill* a
purpose, not *as* a purpose.  Originally, it was the only way to make
32-bit DOS programs *at all*.  Then it was the only 32-bit Windows
way.  Then it was a way to get direct hardware access.

These days, MinGW and Linux cover most of the purposes DJGPP was
originally created for - free software, high quality code, 32- and
64-bit environments, etc.

DJGPP still serves some needs, like direct hardware access and DOS
boot disks, but let's not make more work for outselves when others
have already done it.