From:	Derek Greene <topcoder AT mindspring DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Teaching a child to program in C
Date:	Thu, 10 Sep 1998 02:31:30 -0400
Organization:	MindSpring Enterprises
Lines:	20
Message-ID:	<35F77242.CDBE6D26@mindspring.com>
References:	<35F602EB DOT 5228464C AT mindspring DOT com> <3 DOT 0 DOT 5 DOT 16 DOT 19980909145911 DOT 33e78d5a AT mail DOT geocities DOT com>
Reply-To:	colskywalker AT thepentagon DOT com
NNTP-Posting-Host:	user-37kb5f0.dialup.mindspring.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

So buy the second volume.  Frankly though, pointers aren't the complex
monsters people make them out to be, the big problem is that they are
difficult to explain.  Get past that and you're ok.   A problem i've seen in
the IRC, C and C++ chat rooms, is that people say "Explain pointers to me!?"
and that isn't gonna get you anywhere.  It's easier to explain them when they
can ask more specific questions.

Derek Greene

John Meyer wrote:

> At 05:12 PM 9/9/98 +0100, you wrote:
> >> Buy a ' x For Dummies' book like Qbasic Programming for Dummies, C for
> >> Dummies, et cetera, they are written in a form a baby could understand
> >> (and that's probably not far beyond the truth :-).
>
> Sorry, I've seen too many C and C++ for Dummies books to seriously
> recommend those to anybody.  For instance, C for Dummies doesn't even get
> to pointers until volume two.

- Raw text -