Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!wuarchive!julius.cs.uiuc.edu!apple!apple.com!casseres
From: casseres@apple.com (David Casseres)
Newsgroups: comp.sys.mac.programmer
Subject: Re: From Pascal to C without a hitch ?
Message-ID: <10741@goofy.Apple.COM>
Date: 17 Oct 90 16:26:40 GMT
References: <1990Oct17.151226.2449@fennel.cc.uwa.oz.au>
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 46

In article <1990Oct17.151226.2449@fennel.cc.uwa.oz.au> 
b_murphy@fennel.cc.uwa.oz.au writes:
> So, lets say your a wiz-bang programmer in Pascal ... and your new boss 
(due to economics)
> decides that you are to create code in C or C++ for Windows 3 on
> I*M (I *didn't* say it, I _Just_ hinted a few letters :-)
> 
> What do you recommend for reading. (I speak PASCAL, 6502, Clipper
> BASIC :-(, English and Dutch :-))

I recommend reading a lot of C code, with Kernighan and Ritchie's "The C 
Programming Language" at hand to help you figure out what it means.  Read 
stuff like the sample code that comes with MPW or Think C.  Forcing 
yourself to understand examples is the only way you will ever learn this 
"language."

After you have a reasonable grasp on C (like your typedef's compile two 
times out of three, and you laugh bitterly when people talk about C's 
"portability"), you are ready for C++.  It is really much better than C.  
However, it is still based on C, so a good deal of it doesn't make sense 
except in a very obscure way.  TAKE A COURSE.  You don't want to be alone 
when you're learning C++.

Read Stroustrup's "The C++ Programming Language."  Read it when it's time 
for you to get some sleep, but you can't because you're so terrified by 
what they tried to teach you in the class.  Reading Stroustrup is just 
like getting whacked between the eyes with a 2x4.

When you're awake again, read the "Unofficial C++ Style Guide" by David 
Goldsmith and Jack Palevitch, in issue #2 of Apple's "develop" magazine.  
Everything in it is extremely good advice and it will save you a good deal 
of grief.

Get your hands on some example C++ code, such as what you get with MPW C++ 
or what gets handed out in the course you're taking.  Read, study, force 
yourself to understand -- but much more important, start every C++ project 
by COPYING AN EXAMPLE, and then start changing things and adding your own 
stuff.  This is a major key to successful C++ coding.

Try to avoid reading most books on object-oriented programming.  They will 
tend to make you hate C++.

Write all your comments in Dutch   ; ^ )   ; ^ )   ; ^ )

David Casseres
     Exclaimer:  Hey!