It's UWAweek 47

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 3 articles in this topic
Showing 3 of 828 articles.
Currently 101 other people reading this forum.


 UWA week 35 (2nd semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful
2:53pm Wed 28th Aug, ANONYMOUS

The project requirements state that we need to catch usage errors and syntax errors. While it is stated that syntax errors must be reported to stderr beginning with a "!", I'm not sure what the following "@" character for debug printing is referring to. My thoughts are that Usage errors from the command line will be caught like we have been doing in the labs previously ("Usage:..."), while with the syntax errors we might print ("!Syntax Error"). Would the debug printing be another line after that commencing with "@" which would detail more explicitly what the syntax error is? Do we even need to explicitly detail what kind of syntax error occurred? Thanks.


SVG not supported

Login to reply

👍?
helpful
3:24pm Wed 28th Aug, Christopher M.

ANONYMOUS wrote:
> The project requirements state that we need to catch usage errors and syntax errors. While it is stated that syntax errors must be reported to stderr beginning with a "!", I'm not sure what the following "@" character for debug printing is referring to.
Syntactic errors in an ml program should be reported on a line beginning with a '!', such as ! unrecognised statement They are different to any other debug statements that you wish to print out, such as @ now in function process_statement which you may use to simply explain (to yourself) what your runml program is doing, or where it's up to. Make more sense?


SVG not supported

Login to reply

👍?
helpful
7:04pm Sun 1st Sep, Wandi P.

Hello! Thank you for explaining! I still have a question. Does this mean that there shouldn't be any "@" statements in the official submission since it is for your own debugging? Or it's okay to submit without removing the debugging statements as long as they commence with "@"? Or is it required to write some "@" statements in the final submission? Thank you!

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