It's UWAweek 9 (1st semester, week 1)


This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 2 other people reading this forum.

 UWA week 42 (2nd semester, week 12) ↓
SVG not supported

Login to reply

1:15pm Wed 18th Oct, Christopher M.

> The marking rubric says "The detection of any problems with opening and reading directories, copying files, and memory allocation, should result in an error message being printed, and the program immediately terminating"
Which is consistent with what the project sheet has always said.
> Does this mean that after printing the error message, the next line of code has to be the exit() function? My implementation before seeing the rubric was to return from the current function that was running, then free all the allocated memory, and then exit() rather than abruptly exiting with unfreed memory, unclosed files/dirs, etc. I was wondering if this approach would be marked down or not?
There's no real need to free memeory on termination - [help2002] nor to close files or directories unless you need to flush a file's modified contents to disk.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy