🚀 go-pugleaf

I am looking for some input on C compilers here... I have LATTICE C (not
the latest version) and MEGAMAX C.  As awful as some people say that LATTICE
is on the ST, it has one thing going for it... you can port to it.
When I write portable code (hah!) on my PC or VAX/VMS, I can port it easily
to LATTICE C.  Megamax is hopeless.  It just doesn't have enough functions.
LATTICE is missing some functions that are available on the PC versions, but
it has quite an extensive function library. (Some of the missing things
include TIME functions and variations on exec()).  Sure, LATTICE is slow and
produces HUGE binaries...

The question is this:  Is Mark Williams C for the ST comparable to Let's C
on the IBM?  It has a REAL honest to goodness decent function library!
I have seen rave reviews of the compiler in this digest, but how does it
really compare with the IBM PC compilers?  After years of people drilling
portable code design into me, I find that I have trouble porting to the ST.
Even if I have machine dependent parts in my code, knowing that my ST compiler
can support TIME functions and stuff like temporary-file functions, can
really help in porting.

BTW, does any ST compiler support SIGNALS? (like trapping ~C and other
interrupts)

         _____________________________________________________________
        |                   maroC ddoT | Todd Coram                   |
        |         tcoram@udcvax.bitnet | tentib.xavcdu@maroct         |
        |                   remmargorP | Programmer                   |
        | retneC retupmoC cimedacA CDU | UDC Academic Computer Center |
        |_____________________________________________________________|

"Put a quarter in the juke; boogie 'till ya puke."