Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!ncar!tank!gargoyle!igloo!miroc!caw
From: caw@miroc.Chi.IL.US (Christopher A. Wichura)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A68k vs Lattice 'C'
Keywords: asm a68k lattice
Message-ID: <1551.AA1551@miroc.Chi.IL.US>
Date: 25 May 90 23:57:42 GMT
References: <2196@dsacg3.dsac.dla.mil> <136136@sun.Eng.Sun.COM>
Followup-To: comp.sys.amiga.tech
Lines: 33

In article <136136@sun.Eng.Sun.COM> (Chuck McManis) writes:
>In article <2196@dsacg3.dsac.dla.mil> ( Michael S Figg) writes:
>>How does learning assembly on the Amiga with A68k differ from using the
>>assembler with Lattice 'C'? Are there substantial differences? Do I gain
>>much from using one over the other?
>
>Well I don't know but I do know that Xoper which is supposed to assemble
>with the A68k assembler does _not_ assemble with the Lattice asm assembler.

Nor do many other things.  I have long since abandoned the Lattice asm due
to its bugginess (sp?).  It often complains that perfectly legal
instructions are invalid, etc.  When sending the source though anything
else, such as A68k or Cape v2.0, though, no errors are generated.  I have
also had asm assemble correctly, but produce a corrupted object file.  All
in all, the only time I use it is when I need a variable name of the type
'@name' as Cape (which I primarily use) chokes on Lattice regesterized
labels.  And even then I sometimes just use DEFINES during the BLink
phase...  Asm is also one of the slowest assemblers around, too.

So my advice to M. Figg:  Stay as far away from Lattice's asm as you
possibly can!

-=> CAW

/////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
                          Christopher A. Wichura

               caw@miroc.chi.il.us      (my amiga)         
               u12401@uicvm.uic.edu     (my school account)

Please! Do not send mail to my school account unless mail to miroc bounces.
    I often do not check uicvm.uic.edu for periods in excess of a week.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\//////////////////////////////////////