Message-Id:	<199704210823.KAA00497@math.amu.edu.pl>
Comments:	Authenticated sender is <grendel@[150.254.113.14]>
From:	"Mark Habersack" <grendel AT hoth DOT amu DOT edu DOT pl>
Organization:	PPP (Pesticide Powered Pumpkins)
To:	pierre AT tycho DOT com
Date:	Mon, 21 Apr 1997 10:24:22 +0100
MIME-Version:	1.0
Subject:	Re: Usage of directory entries
Reply-to:	grendel AT hoth DOT amu DOT edu DOT pl
CC:	opendos-developer AT delorie DOT com
References:	<Pine DOT BSI DOT 3 DOT 96 DOT 970418161551 DOT 23833E-100000 AT hoth DOT amu DOT edu DOT pl>
In-reply-to:	<Pine.LNX.3.95.970418154326.27261H-100000@55-174.hy.cgocable.ca>

Once upon a time (on 18 Apr 97 at 15:44) Pierre Phaneuf said:

> On Fri, 18 Apr 1997, Mark Habersack wrote:
> 
> > Won't happen IMHO. That would require too much work and practically
> > implementing a new compiler from scratch. DJGPP has been created on 32-bit
> > and even 64-bit machines and not on 16-bit oldies. Don't forget that the
> > main source is for Unix, DJGPP is "just" a port - DJ doesn't write it from
> > scratch. You cannot expect GCC guys to work on a product they are not
> > going to use.
> 
> Ok, so this is out of question... Now, what 16-bit free C compiler is good
> enough? And preferably compatible enough with GCC to share
> #DEFINE/#IFDEF-laden sources?
Did anyone check the Linux16 project? The BCC compiler there is supposed to 
work also on DOS. And there's that Micro-C shipped with FreeDOS - it's quite 
limited tho.
==================================================
Stand straight, look me in the eye and say goodbye
Stand straight, we drifted past the point of
  reasons why.
Yesterday starts tommorow, tommorow starts today
And the problems seem to be we're picking up the
  pieces of a ricochet...

- Raw text -