Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!agate!eris!doug
From: doug@eris (Doug Merritt)
Newsgroups: comp.sys.amiga
Subject: Re: 'void *' (was Re: malloc() prob. on 3.4a)
Message-ID: <9030@agate.BERKELEY.EDU>
Date: 21 Apr 88 07:54:43 GMT
References: <8804200436.AA22240@cory.Berkeley.EDU>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: doug@eris.UUCP (Doug Merritt)
Organization: University of California, Berkeley
Lines: 22

In article <8804200436.AA22240@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>	It sounds like you aren't sure of your own code.  I don't make
>those kind of mistakes.

I hope you knocked on wood when you said this. It may be that you
avoid this in general. Let me know if you continue to hit 100%
perfect on the subject now that you claimed it. 1/2 :-)

>to be told twice, and when I read my source 10 years from now it will
>look as clear cut and clean and understandable as it did when I first 
>wrote it.

Well. Maybe. Thin ice. You may be the exception to the general rule,
but I hope you're aware in general that people believe this more often
than it's the actual case. When I look at C programs I wrote 10 years
ago, I'm more often proud of the ideas than the actual implementation.
Maybe you're a lot better than I ever was. That's good. But be cautious,
just in case. There's no gain in convincing yourself that your current
level of expertise will be your maximum in the future; that tends to
limit your own future learning and growth.
	Doug Merritt		doug@mica.berkeley.edu (ucbvax!mica!doug)
			or	ucbvax!unisoft!certes!doug
			or	sun.com!cup.portal.com!doug-merritt