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


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

Login to reply

👍x1
helpful
9:36pm Thu 5th Sep, ANONYMOUS

Hello,

Section 4 of the project requirements says that:

All syntax errors detected in invalid ml programs must be reported via stderr on a line commencing with the '!' character. Your runml program must be able to detect all invalid ml programs - EXCEPT that your program will not be tested with any invalid expressions, so you do not need to validate the syntax of expressions.

Which makes sense- but how far does not being tested with "invalid expressions" go? Can we assume that all functions that are called have the correct number of parameters? This is important as it determines whether we must check the parameters for every nested expression against the number of parameters expected- which is a complex splitting issue. We know that "a function must have been defined before it is called in an expression", but can we assume that as long as it has been defined, it will be called correctly?

Thank you


 UWA week 37 (2nd semester, week 7) ↓
SVG not supported

Login to reply

👍?
helpful
8:35pm Wed 11th Sep, Joshua N.

ANONYMOUS wrote:

Hello,

Section 4 of the project requirements says that:

All syntax errors detected in invalid ml programs must be reported via stderr on a line commencing with the '!' character. Your runml program must be able to detect all invalid ml programs - EXCEPT that your program will not be tested with any invalid expressions, so you do not need to validate the syntax of expressions.

Which makes sense- but how far does not being tested with "invalid expressions" go? Can we assume that all functions that are called have the correct number of parameters? This is important as it determines whether we must check the parameters for every nested expression against the number of parameters expected- which is a complex splitting issue. We know that "a function must have been defined before it is called in an expression", but can we assume that as long as it has been defined, it will be called correctly?

Thank you

If no clarification is given, better to be safe than sorry and check the number of parameters.

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