Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!edcastle!lfcs!nick From: nick@lfcs.ed.ac.uk (Nick Rothwell) Newsgroups: comp.sys.mac.programmer Subject: Re: Think C 4.0 comments (LONG) Keywords: THINK Lightspeed C Message-ID: <418@castle.ed.ac.uk> Date: 15 Sep 89 12:58:48 GMT References: <13638@well.UUCP> Sender: root@castle.ed.ac.uk Reply-To: nick@lfcs.ed.ac.uk (Nick Rothwell) Organization: LFCS Enya Admiration Society Lines: 32 In-reply-to: wdh@well.UUCP (Bill Hofmann) In article <13638@well.UUCP>, wdh@well (Bill Hofmann) writes: >Interface: >1. Sounds for error and completion: while it IS lightspeed, it still takes > light 8 minutes to reach the earth from the sun. A few weeks ago, I had this wonderful idea - use the RAM cache! Never thought of it before, since hardly anything else seems to like the RAM cache that much, but TC runs like a dream - sometimes, NO disk access at all to compile a module, even for the #includes. >2. More functionality in the editor. It's fast, and I love the balance > command, but here are some other suggestions: One thing I'll scream for in the editor - the ability to have two views on one file, perhaps as a window split or something. I'm always having to look at a struct declaration at the top of a file and use it lower down. I'm too used to EMACS, I suppose. >3. Of course, I would love a set of 100% compatible Rez and Derez tools so I > didn't have to run MPW all the time. RezTools doesn't cut it, because I > have multiple .r files. Face it guys, RMaker is a stone-age product. I use ResTools a lot, with several .r files. I just have a top-level .r file which pulls in the .rsrc files from the lower ones. So, you have to issue more commands, but it seems fine. Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk !mcvax!ukc!lfcs!nick ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Fais que ton reve soit plus long que la nuit.