home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.msdos.programmer:3032 comp.os.msdos.programmer:11660 comp.sys.ibm.pc.programmer:691 comp.lang.c++:18470 comp.lang.c:18938
- Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer,comp.sys.ibm.pc.programmer,comp.lang.c++,comp.lang.c
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!udel!princeton!mccc!pjh
- From: pjh@mccc.edu (Pete Holsberg)
- Subject: Re: Newbie Wants Advice on C-Programming
- Organization: The College On The Other Side Of Route One
- Date: Mon, 28 Dec 1992 18:23:53 GMT
- Message-ID: <BzzF3u.8M1@mccc.edu>
- References: <1992Dec24.154204.25248@blkbox> <1992Dec24.230420.4243@sequent.com> <1992Dec25.050515.20871@ncsu.edu>
- Lines: 22
-
- In article <1992Dec25.050515.20871@ncsu.edu> bank@lea.csc.ncsu.edu (Belgarath the Sorcerer) writes:
- =4) Even if you're not going into OOP, do NOT take up Pascal as
- = a road to C. Pascal is a language that assumes you know
- = very little and places lots of restrictions and
- = inhibitions on you. If you already are a traditional-style
- = programmer, you don't need the knowledge Pascal will
- = teach you (modularization, declaration, etc). Go on into
- = C and avoid having to unlearn all the limits Pascal will
- = place on you.
-
- For a person who does not know structured programming ideas, Pascal is a
- must. The people who have the most difficulty (in my experience in
- teaching C) are those who are experienced in COBOL, BASIC and FORTRAN.
-
- =5) Picking up Assembler prior to learning C isn't a bad idea.
- = Hardly required, tho.
-
- Many explanations of what C can do (and more importantly, what you did
- wrong in your program) are best explained to a person who knows what a
- computer does and how it does it, a background that is acquired fairly
- easily by learning any assembly language. IMO, of course.
-
-