Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcsun!ukc!edcastle!dcl-cs!gdt!gdr!mapjilg
From: mapjilg@gdr.bath.ac.uk (J I L Gold)
Newsgroups: comp.sys.amiga
Subject: Lattice C V5.0
Message-ID: <1989Nov10.143425.14184@gdt.bath.ac.uk>
Date: 10 Nov 89 14:34:25 GMT
References: <3147@nigel.udel.EDU> <614@milton.acs.washington.edu> <13149@s.ms.uky.edu>
Reply-To: mapjilg@gdr.bath.ac.uk (J I L Gold)
Distribution: comp.sys.amiga,comp.sys.amiga.tech
Organization: University of Bath, England
Lines: 22

I'm having a few problems with my new Lattice C compiler. I realise I
should get the V5.4 upgrade, but seeing as Lattice don't SEEM to have
UK representatives that may take a while. In the meantime, I'm running
it on an A500 with 1Meg with an external floppy (can't afford a hard
disk at the mo). The "Hokey-cokey" compilation process ("You put the
left one in, the right one out, you do the hokey-cokey and you shake
it all about") seems to prevent me from optimising with lc -O ....
I get "Command 'go' not found". GO is on disk #3 so I guess I should
use some combination of assign and path. Maybe some of you out there
can help?
 Also, V1.0(!?) of CodeProbe seems to crash more often than not, even
when debugging the test program ftoc.c. To make life easy for myself,
I put the source into RAM:, put disk #3 in df1:, type cd RAM: and then
df1:c/cpr ftoc after compiling with the -d3 option. The debugger crashes
when I execute the "go" (ie the run program) command. It also crashes
when I do the same with the lines program, except it crashes when I
step through the code and reach the OpenWindow(&nw) line. There's a
guru for this crash which means illegal library call or something. 
 Help on these matters would be much appreciated. Reply to newsgroup
or email mapjilg@uk.ac.bath.gdr
	Cheers,
		Julian Gold.