home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!void!jbrowne
- From: jbrowne@void.ncsa.uiuc.edu (Jim Browne)
- Subject: Re: A few more suggestions for THINK C
- References: <SJE.92Jul20180620@xylos.ma30.bull.com> <SRO.92Jul21221949@media-lab.media.mit.edu> <1992Jul22.103153.14800@doug.cae.wisc.edu>
- Message-ID: <jbrowne.711831043@void>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Distribution: comp
- Date: Wed, 22 Jul 1992 18:50:43 GMT
- Lines: 18
-
- jverdega@cae.wisc.edu (Jeffrey Verdegan) writes:
-
- >>What would be useful is if THINK C would log code swaps for you
- >>while you're developing the code. Then, if you notice that there
- >>is a lot of unrest on the heap, you can consider reassigning
- >>project entries from one segment to another. It may already do
- >>this.
- >>
-
- I just usually generate a link map. I can almost always find what I need in
- there.
-
-
- --
- Jim Browne | jbrowne@ncsa.uiuc.edu |
- NCSA/STG System Administrator | stgadmin@ncsa.uiuc.edu |
- System Administration: Where the fun never ends... | (217) 244-7798 |
- --"It's really weird... kind of like how Telnet is programmed." - Q. Koziol --
-