Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!network!ucsd!orion.cf.uci.edu!uci-ics!zardoz!ccicpg!cci632!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!sunybcs!rutgers!sun-barr!ames!hc!lll-winken!uunet!microsoft!paulc
From: paulc@microsoft.UUCP (Paul Canniff 2/1011)
Newsgroups: comp.lang.c
Subject: Re: What's a C expert?
Message-ID: <6057@microsoft.UUCP>
Date: 22 Jul 89 06:08:53 GMT
References: <12214@well.UUCP>
Reply-To: paulc@microsoft.UUCP (Paul Canniff 2/1011)
Distribution: all
Organization: Microsoft Corp., Redmond WA
Lines: 31

In article <12214@well.UUCP> tmh@well.UUCP (Todd M. Hoff) writes:
>After a few lengthy arguments nobody could satisfactorly answer
>this question:
>
>           What do you need to know to be an expert C programmer?
>
>Any takers?
>
>
>Todd

The obvious smug answer ... if you have to ask, you aren't.

Sorry, couldn't resist.  And I can't think of a really good, serious
answer.  I mean, how do you rate an expert?  I consider myself
pretty good, but sometimes I still check the operator-precedence
charts.  

How about ... understands why a[i] equals i[a] and CAN EXPLAIN IT,
knows what a trigraph is, and can tell why the following code
prints "false" (on 8-bit char systems).

	char x = 0xff;

	if (x != 0xff)
		printf("FALSE\n");


------------------------------------------------------------------
Disclaimer blah blah humorous statement blah blah Microsoft blah
blah blah ... you get the idea.