It's UWAweek 45 (2nd semester, 2nd exam week)

help2002

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 the 2 articles in this topic
Showing 2 of 827 articles.
Currently 6 other people reading this forum.


 UWA week 38 (2nd semester, week 8) ↓
SVG not supported

Login to reply

👍?
helpful
2:01pm Tue 17th Sep, ANONYMOUS

Is it correct that the syntax assumptions in the report do not have to align with the advice given on this help forum? Such as if global variables, variable reassignment and parameter checking have already been implemented, they can be listed as assumptions and we shouldn't lose marks for adding those checks. Thanks


SVG not supported

Login to reply

👍?
helpful
3:30pm Tue 17th Sep, Joshua N.

ANONYMOUS wrote:
> Is it correct that the syntax assumptions in the report do not have to align with the advice given on this help forum?
I mean a lot of the advice given on the forum is based off the project requirements and clarifications Chris made, so it really depends on which advice you are talking about. A rule of thumb for assumptions is: If you make an assumption that goes against the project specification or what Chris or Amitava said to do you will lose marks. Otherwise for ambiguities where no clarification was given or I made it clear it is up to Amitava then you can list that in the assumptions.
> Such as if global variables, variable reassignment and parameter checking have already been implemented, they can be listed as assumptions and we shouldn't lose marks for adding those checks. > > Thanks
You definitely won't lose marks for doing more work if that's what you are asking? It demonstrates your ability to write robust C code, which is good.

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  8:08AM Aug 25 2024
Privacy policy