1
edit
Changes
m
Commenting within As well, please ensure that a small commented header is at the function top of every file (implementation if .cpp or header if .h). It should contain information such as the file name, project name, last modified date, last modified by, etc...Using the example of ciol.c from assignment 1, it should be generally organizedin the following form:<pre>/* ########################################################################## Project: OOP344 Assignment 1 File Name: ciol.c File Desc.: Implementation file for console input output (CIOL) library. Last Modified By: Hasan Kamal-Al-Deen Last Modified On: October 14, 2009 ##########################################################################*/</pre>Now SVN can actually automatically change the "last modified" lines as you commit files to the repository but we'll have to work that's out after we know a bit more about it for in-function commentingthe assignment.For the time being, we'll have to update files manually :)<br/><br/>
→Comment Blocks OOP344 northWind87: added a part to the comment block section explaining file headers
char* io_strcpy(char* dest, const char* src, int n){
</pre>
Commenting within the function should be generally organized, that's about it for in-function commenting.
That's about it folks, feel free to add or remove anything if you feel so compelled but please consult the rest of the group first if it is a major change.<br/>
'''-northWind87'''
