154
edits
Changes
→OOP244/BTP200
* first draft completed including file objects, function templates and abstract base classes
* standards history brought up to date
* to be done for the next draft** a few more diagrams to be added** outcomes and quotes to be reviewed** which sections are optional** should anything else be included
* Danny A disagreed to adding abstract base classes, function templates and file objects and voiced his concern that there was barely enough time to introduce inheritance - although there was no consensus reached on this point, Chris S will move forward with the additions and we will see what happens
* Sorry I am late to respond, generally I agree we should follow Chris S notes and I would like encourage newer practices found in C11 for IPC144/OOP344, and in C++0x for OOP244/OOP344. This means stuff like using auto to let compiler decipher type, nullptr to initialize pointers. Students should also learn how to debug programs that are not working based on error messages from compiler, crashes, incorrect programming practices. Making a mistake is ok but repeatedly not initializing pointers, local variables, etc. is a common reason for frustration. Just my thoughts - MF
==== Issues Raised and Resolved - First Draft ====* method or member functions- revert to member functions for C++* start with using namespace std; and cout - then switch to std::cout from halfway through the notesonce header file requires iostream - header file should not include using namespace std* unit tests - two sections added - in Modular Programming (week 1) - in Abstract Base Classes (week 11)==== Issues Raised - still unresolved - Final Draft ====* which sections should be optional in 244 - still undecided* move copy ctors and = ops just after Current Object* move virtual functions and abstract base classes ahead of templates
=== OOP344/BTP300 ===
