home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!milton!chuckb
- From: chuckb@milton.u.washington.edu (Chuck Bass)
- Newsgroups: comp.lang.c
- Subject: Re: Most difficult part of learning C?
- Message-ID: <chuckb.714781695@milton>
- Date: 25 Aug 92 22:28:15 GMT
- References: <9208251159.AA04122@ult4> <1992Aug25.180919.10370@samba.oit.unc.edu> <behrenss.714775792@hphalle6>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington
- Lines: 24
-
- I think that often times things that are difficult to learn
- about a language are really caused by not knowing much about
- programming. If the concept of a pointer is not somewhat clear
- then using scanf will be "difficult". Not because of C but
- because of not understanding a concept that C is based on.
-
- I would bet that assembly language programmers have no problem
- picking up C's notion of pointers. I admit that for me pointers
- and arrays, and pointers to char took a while to understand. I
- attribute this to the fact that before C I knew a bit of basic
- and a bit of Scheme. Two languages where pointers were not
- introduced to me.
-
- Anyway, I found precedence and type casting to be very
- confusing. I still use cdecl if there is any question when I
- need a pointer to a function returning pointer to ...........
-
- Just my 0.02...
-
-
- Chuck Bass
- College of Forest-Systems Engineering
- University of Washington
- chuckb@u.washington.edu
-