"Harrison Lisle" [email protected] wrote:

Hello,

Hi Harrison

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?

Sorry for the delay, unfortunately, there's been sudden changes to the teaching staff, so I have to wait for the new unit coordinator to clarify these questions.

The second is in the inconsistencies between how functions are called between examples. ... Where there is clearly a space between the two. Which is the right option?

Answered here https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=U201

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

perror is used for system call errors. As system calls have specific error numbers, perror interprets those numbers to create the error message. For this project you need to make custom error messages, to do this use fprintf, as shown below:

fprintf(stderr, "!error message");

Answered here: https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=U172

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?

Answered here: https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=U153

Thanks. np