Date: Tue, 09 Sep 1997 14:39:48 +1100
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: differences
In-reply-to: <341467B3.6610@cs.com>
To: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp AT delorie DOT com
Message-id: <199709090244.OAA08721@teleng1.tait.co.nz gatekeeper.tait.co.nz>
Organization: Tait Electronics Limited
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Comments: Authenticated sender is <billc AT blackmagic DOT tait DOT co DOT nz>
Precedence: bulk

On  8 Sep 97 at 21:01, John M. Aldrich wrote:
> Main differences between djasm and gas:
[snip]
>  - djasm is undocumented and not 100% complete; gas is fully
>  supported 

I'm working on it. More adding features than documenting it, however.

>  - djasm code cannot be linked with DJGPP programs;

Not quite true. djasm can link coff files, but only to the generated 
exe file, not the other way round. Morten Welinder (sp?) used 
(created?) the feature for his dpmi server.  Unfortunatly for us (the 
djgpp community), mwdpmi got moth-balled.

> 
> Users should use gas, or an alternative 32-bit assembler like nasm,
> for normal programming purposes.

That is so completely, utterly and absolutly true, it's not funny. I 
only use djasm for my 16 bit projects (mostly boot sectors, but I'm 
going to use it for my own lfn driver), otherwise, I use gas and I am 
trying to port the OpenDos sources to NASM.

As the old saw goes: use the right tool for the job. (I don't use 
NASM for 16 bit code as I don't (yet) have a 16 bit linker).
Bill
--
Leave others their otherness.