home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c:12413 comp.programming:2350
- Path: sparky!uunet!ogicse!plains!news.u.washington.edu!milton!chuckb
- From: chuckb@milton.u.washington.edu (Chuck Bass)
- Newsgroups: comp.lang.c,comp.programming
- Subject: Re: Allocate memory to typed in string, How?
- Message-ID: <chuckb.714033994@milton>
- Date: 17 Aug 92 06:46:34 GMT
- Article-I.D.: milton.chuckb.714033994
- References: <1992Aug13.184911.376@wyvern.twuug.com> <1992Aug15.201359.3601@athena.mit.edu> <1992Aug16.211644.6444@athena.mit.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington
- Lines: 24
-
- I've been programming for a couple of years now and I must say
- that at first I though all of this BS about not using buffers
- that "should be plenty big" was just that. A bunch of anal
- perfections with nothing better to do than flame others coding
- practices.
-
- Now I've been bit by failed assumptions that occur when source
- is modified and now that routine that assumes a NULL ptr can
- never be passed is. Well people, listen to what these guys are
- saying. Program defensively and you will have robust code that
- won't break (as much ;-) I thought I was smart enough to write
- code that didn't require things like Assert or Assure (as
- recently posted here in comp.lang.c) Now I've realized that I'm
- at the point that I'm smart enough to use the Assert and Assure
- macros.
-
- Just a word of experience from someone with almost no
- experience. Anyway writing programs is a lot more fun that
- debugging them!
-
- Chuck Bass
- Cooperative for Forest-Systems Engineering
-
- PS for some reason I always agree with Mr. Summit!
-