home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!decwrl!csus.edu!netcom.com!netapp
- From: netapp@netcom.com (Byron Rakitzis)
- Subject: Re: Most difficult part of learning C?
- Message-ID: <sacngxn.netapp@netcom.com>
- Date: Thu, 27 Aug 92 05:45:08 GMT
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- References: <9208251159.AA04122@ult4> <1992Aug26.124652.9509@alw.nih.gov>
- Lines: 22
-
- Pointers: Learning the difference between different types of pointers,
- and the issue array-pointer confusion.
-
- Declaration syntax: declaring arrays of function pointers, for example,
- is something I occasionally have to drag out cdecl for to this day.
-
- Operator precedence: the precedences are hard to learn, also order of
- evaluation of expressions is something that can bite you while learning
- C. e.g., here's a hypothetical error a tyro could easily make:
-
- int read100() {
- return ((getchar()-'0')*10) + (getchar()-'0');
- }
-
- (and never mind not checking the return value of getchar() for now.)
-
- A very confusing example in this vein is arglists: syntactically they
- resemble a comma-separated list of expressions, but unlike a comma-
- separated list of expressions, left-to-right order of evaluation is
- not guaranteed.
-
- I guess I should add typedefs, too. They took a while to understand.
-