Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I may have to give a crash course in c++ for a data structures class. Any suggestions on what would be essential for me to go over other than classes? thanks in advance

I forgot to mention I am not a teacher but a tutor and I need to help some fellow students get up to speed quickly so that they don't fall behind then I can hopefully fill in the gaps.


migration rejected from stackoverflow.com Mar 2 '14 at 16:26

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as too broad by gnat, Bart van Ingen Schenau, MichaelT, Michael Kohne, GlenH7 Mar 2 '14 at 16:26

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. If this question can be reworded to fit the rules in the help center, please edit the question.

C++ wouldn't be my choice of language for teaching anything other than C++. –  Anon. Jan 25 '11 at 3:31
Someone who has to ask what to teach in a C++ course wouldn't be my choice of teacher for teaching C++ :-) –  paxdiablo Jan 25 '11 at 3:33
Does it mean you are the teacher who is going to explain to the students? –  vz0 Jan 25 '11 at 3:33
This is what's wrong with computer science education today. –  John Dibling Jan 25 '11 at 3:44
Will such crash course produce any good programmers? –  Mudassir Jan 25 '11 at 4:15

1 Answer 1

Pointers or no pointers, that is the question. It's unfortunately so heavily ingrained in c++ that it's not something you can avoid, however arguably pointers are the most confusing part of c++ and if your students aren't professional programmers, most likely only half of them will grasp pointers and the other half will pretend they do.

So with that said, if they're somewhat seasoned programmers, I would try to cover it simply in the context of "referenced parameters" and the like. That's easy enough to understand without getting into too much detail. Details can come later.

Stick to examples and explain them which parts of the code are subject to change and which parts must be a certain way. Might seem obvious to one who knows c++ but without any experience, that becomes very important.