home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / comp / sys / mac / programm / 14339 < prev    next >
Encoding:
Internet Message Format  |  1992-08-21  |  766 b 
  1. Path: sparky!uunet!caen!uflorida!cybernet!pollansw
  2. From: pollansw@cse.fau.edu (Warren Pollans)
  3. Newsgroups: comp.sys.mac.programmer
  4. Subject: C function bookkeeping tool?
  5. Message-ID: <1992Aug21.201644.9092@cybernet.cse.fau.edu>
  6. Date: 21 Aug 92 20:16:44 GMT
  7. Sender: news@cybernet.cse.fau.edu
  8. Organization: Florida Atlantic University, Boca Raton, FL, USA
  9. Lines: 14
  10.  
  11.  
  12. Is there an "accepted" way of keeping track of functions in a long
  13. C program.  All I could think of is keeping a list (another file)
  14. of functions with: the files in which they're located, the variables
  15.  they need, the functions they call, the
  16. global variables used and changed, etc.  I'm sure that someone must
  17. have already figured out a good way to do this.
  18.  
  19.  
  20. Thanks,
  21.  
  22.  Warren
  23.  
  24. (pollansw@cse.fau.edu)
  25.