Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!mtxinu!unisoft!hoptoad!fidogate!f444.n161.z1.FIDONET.ORG!Jim.Lynch
From: Jim.Lynch@f444.n161.z1.FIDONET.ORG (Jim Lynch)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C Suggestions
Message-ID: <8911.273F5352@fidogate.FIDONET.ORG>
Date: 10 Nov 90 06:50:26 GMT
Sender: ufgate@fidogate.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:161/444 - BMUG, Berkeley CA
Lines: 17

Hi, I'm new here but here's my suggestions:
1) have Think C work more like Turbo C: if it detects errors/warnings in the 
files, it keeps compiling it until the end of the file that the error was in 
(or until too many errors) and allows you to select an error which will take 
you to the point in the source where it occured.  Also, Think C says 'Syntax 
Error' too much.  I want to know WHICH syntax rule was violated.
2) Turbo C remembers the debug settings (i.e., what vars are being watched, 
etc). Think C is great but there's room to improve it without making it too 
complex.
3) Please let me use microEMACS and interface to it in such a way that it 
would go to that editor when errors occur.  MicroEMACS is capable of this, I 
believe.

--  
Jim Lynch - via FidoNet node 1:125/777
    UUCP: ...!uunet!hoptoad!fidogate!161!444!Jim.Lynch
INTERNET: Jim.Lynch@f444.n161.z1.FIDONET.ORG