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 7 other people reading this forum.

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

Login to reply

5:38pm Thu 19th Oct, Christopher M.

> I've come across a specific edge case, where if you have a file A in one directory then that same file name in another (with one of them being newer). So the program then tries to sync the newer file to the older file by opening it. However, if the older file has restricted permissions (errors out on open), should the program exit and report why. > Or should it delete the old file and then create it again with the required perms (default or carried over)?
What does the project sheet say about detecting and handling errors?
> Additionally, if the newer file is smaller than the old file, the old file may be left with artifacts of the old copy (which is a result of our code). Is there a way to wipe the file's contents before writing to it? or should it just be simply deleted if one exists before syncing to it?
Investigate the creat() system-call.

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