For content, expect similar content to the first exam, so all revision hints still apply.
However, there is at least one question which needs you to write some linked list code from scratch - to show that you can code something up.
Since you don't know the details of the question, which asks you to do specific things, you need to make sure that you can create singly and doubly linked lists, with appropriate data in the list item, and add to the hear, tail, or a specified position.
As somebody said to me last year "Your exam is very like the entrance exams we had for C++ programming jobs". My response was, "Yes, it's deliberate."
You should also note that many questions and examples in the lectures follow the same format as well (again deliberately) so it is worth going back through these too.
I have put a corrected exam paper for 2011/2012 here (G52CPP exam from 2011/2012
If should now give you a good idea of the TYPE of format for this year's exam, although all questions will be out of 20 this year (so that the total of 60 matches the 60% the exam is worth).
Finally, to help you out as you work through the exam, most questions you can cut-and-paste the code into a compiler to see what the output is - which I recommend you do, and play with it until you understand it.
In this version of the paper I have added a bit of text on each question telling you want to look for, which may help you in an exam: Version with hints or answers.
I had some comments about people finding it harder to read code than to write it, so there may be slightly (note the 'slightly'!!!) more 'write code for' in the exam this year than last year.
Older version of G52CFJ exam from 2010/2011
Unfortunately, I don't keep a copy of the exam on the system, and I lost my final copy after submitting it. This is an 'almost' final copy of the 2010/2011 exam. For revision purposes the differences should be irrelevant - it still gives you an idea of exam layout and types of questions.
Questions are mostly relevant, with the following comments:
Change all references to 'C' to 'C++' and change any include file names appropriately. (e.g. stdio.h becomes cstdio)
G52CFJ exam from 2009/2010
Questions are mostly relevant, with the following comments:
Change all references to 'C' to 'C++' and change any include file names appropriately. (e.g. stdio.h becomes cstdio)
Question 1b: Questions comparing C and C++ are less likely, since the module is now C++ not C and C++.
Question 2: This would ask for C++ code rather than C code
Some example answers and comments are here.
G52CFJ exam from 2008/2009
Questions here are mostly relevant, with the following comments:
Change all references to 'C' to 'C++' and change any include file names appropriately. (e.g. stdio.h becomes cstdio)
Question 2: This would consider writing C++ code instead of C code.
Questions 4d, 4e: This would be C++ code using cstdio rather than stdio.h
Some example answers and comments are here.