Message-Id:	<199704221126.NAA17851@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:	jamesl AT albany DOT net
Date:	Tue, 22 Apr 1997 13:28:13 +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
In-reply-to:	<199704221015.GAA18609@keeper.albany.net>
References:	<199704220938 DOT LAA31051 AT math DOT amu DOT edu DOT pl>

Once upon a time (on 21 Apr 97 at 18:18) James Lefavour said:

> > Is it good?
> It's not bad, as far as it goes (There is even an LCC for win32!) but 
> it is C only, and I don't see a complete package =[ just a compiler.
Fine with me ;-)) I don't like C++! ;-))

> The win32 package is complete, but that doesn't help us yet...
But always a nice thing to have - just in case.

> > > BCC can be obtained from : http://epocha.pd.mcs.net/Linux8086/
> > > Thanks.
> > It should be also on sunsite in .../ALPHA/linux16 directory. 
> Unfortunately, bcc is only for .com files... is that enough? Probably 
> not for OD16 ...
So it doesn't produce any object files? Hmm... but it does produce assembler 
output? If so, then all we need is an assembler supporting the format!

BTW. NASM can be used as a back-end for the LCC compiler.
==================================================
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 -