home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!sdd.hp.com!ux1.cso.uiuc.edu!bradley.bradley.edu!camelot!gilligan
- From: gilligan@camelot.bradley.edu (Edward Henigin)
- Subject: Re: Learning C
- Message-ID: <gilligan.728160893@camelot>
- Sender: news@bradley.bradley.edu
- Nntp-Posting-Host: camelot.bradley.edu
- Organization: Your Mother's Knee
- References: <Steve_Mech.04q2@bearsden.UUCP>
- Distribution: na
- Date: 27 Jan 93 18:54:53 GMT
- Lines: 26
-
- In <Steve_Mech.04q2@bearsden.UUCP> Steve_Mech@bearsden.UUCP (Steve Mech) writes:
-
- >What I would like to know is how I should go about learning C.
-
- First off, watch your margins.
-
- Secondly, I would recommend going to your local community college and
- taking a class on C. Should be pretty cheap, and you will probably learn
- things that you may or may not learn on your own.
-
- Thirdly, get a hold of other people's sources, and look at theirs, and
- try to understand why they did what they did. This has proven invaluable
- to me in learning just about anything.
-
- Fourthly, RTFM. You should get about 10 pounds in docs for your compiler,
- and you can learn a lot by leafing through them, because you will pick
- up things you may later want to refer back to and use as reference in your
- projects.
-
- Fifthly, and finally, get projects of your own. Learning by doing, I say.
-
- ed
- --
- | To make do is a promise / Hard to keep without help. -- Helmet |
- | ed -- gilligan@camelot.bradley.edu |
- |----------------------------------------------------------------------------'
-