"Kevin Goodsell" <us************ *********@never box.com> wrote in message
news:Ac******** **********@news read3.news.pas. earthlink.net.. .
fAbs wrote: thanks.
Please don't top-post. Read section 5 of the FAQ for posting guidelines:
http://www.parashift.com/c++-faq-lite/
IM not really reading any.
I got this information from lecture notes.
That's not a very good way to learn C++. Frankly, most C++ teachers
don't know the language well enough to be teaching it (but they usually
believe they do). A good book is about the best way.
Ahem. I teach C++ AND I know it well enough to be teaching it. BUT I lurk
here to learn more.
What I have learned is that I have to teach it wrong first to get ideas
across and then correct what is wrong once students CAN get it right.
Example: C-strings vs. string class. (Or for that matter .h file headers vs.
headers.) To jump into the header usage brings up namespaces and that
requires some feeling for variable allocation. And sometimes students don't
know what a variable is.
There may a good book out there, but I still haven't found a good TEXT,
which a different animal. And the texts used are usually dictated for use by
some committee who is more swayed by the rep (hey! free lunch) than the
contents of the book.
I am currently using a book which is pretty good, but non-standard. Every
example in the book is void main( ), so I teach int main( ) and tell the
student they get no credit for any homework that uses void main( ). Can you
guess what comes in for homework? You bet, void main( ).
With that mindset and low ability to follow instructions I'd be crazy to try
and teach namespaces right off the bat.
I'd much rather prefer they use their lecture notes. Or even take lecture
notes. Or take them down correctly.
The only thing worse than teaching C++ is working next to a guy programming
it with void main( ) and arguing all the time.
--
Gary