It's UWAweek 42 (2nd semester, week 12)

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 selected article
Showing 1 of 738 articles.
Currently 73 other people reading this forum.


 UWA week 36 (2nd semester, mid-semester break) ↓
SVG not supported

Login to reply

👍x1
helpful

Hello,

My first question is one which is halting me and has already been posted about a few times (here and here) but is still yet to be answered. This is regarding the evaluation of non-returning functions. Can these be assumed to be equivalent to 0, or should assigning them cause an error?

The second is in the inconsistencies between how functions are called between examples. In Sample 6 we see the following:

print multiply(12, 6)

with no space between the function call and the brackets with parameters. However in Sample 5 there's this:

printsum (12, 6)

Where there is clearly a space between the two. Which is the right option?

Finally I have two questions about error handling given that there has been no error handling taught thus far within the unit. First- is a standard error message using perror with an undefined error 0 adequate? Such as:

[Custom error message]: Undefined error: 0

Lastly, does every error have to be handled by runml? Are there some errors that are able to be picked up within compilation of the C file, or does every error have to be dealt with specifically by the compiler we've written?

Thanks.

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