Changes

* === IPC144/BTP100===** https://scs.senecac.on.ca/~ipc144/** https://scs.senecac.on.ca/~btp100/** web site, workshops, and exercises have been completed by Chris S** 2012 C11 agreed (see below) changes have been incorporated by Chris S** Cathy L found Chris S' timeline left enough time to cover everything with time left over for review and sick days** adding recursion was raised by several faculty last month - Cathy L and Danny A said that they cover it in detail in DSA555/BTP500 - the meeting decided to exclude this topic from the notes, web sites and subject outline but nevertheless leave instructors free to introduce it in 1st semester** Cathy L does not like the new web site notes** Cathy L has setup a wiki for faculty to collaborate on making their own notes as an alternative to Chris S' notes**: Cathy L has started uploading Evan W's notes to the wiki**: Chris S has added on each page of the web site a link to Cathy L's wiki on matrix** Cathy L noted that not all faculty covered the agreed changes this semester** Sorry I missed the meeting. Anyway FWIW I think we should add more content to IPC144 - such as structs malloc and all operators including bitwise. Just my 2¢....Selmys** Cathy L wanted to add structs also** Chris S produced a pdf that can be printed as a text to be sold in the Bookstore** full changes and the new text are being introduced in Fall 2013** Cathy L has developed videos up to selection constructs* === OOP244/BTP200===*https://scs.senecac.on.ca/~oop244/pages.141/content/index.html* structs removed to IPC144/BTP100** auto added, * keywords filled in, * draft notes done to member operatorsfile objects** adding abstract base classes, function templates and file objects was discussed - Danny A disagreed and voiced the opinion that there was barely enough time to introduce inheritance - although there was no consensus reached 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 * === OOP344/BTP300===** no progressyet** discussions started on Aug 28 2013* how about a section of the course on programming for performance - e.g. move semantics* to what extent should we cover threads - pthreads, compiler directives, language extensions