It's UWAweek 19

helpOSTS

This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

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.

How do I ask a good question?
Displaying selected article
Showing 1 of 411 articles.
Currently 15 other people reading this forum.


SVG not supported

Login to reply

👍?
helpful

"Zachary Baker" <23*5*0*2@s*u*e*t*u*a*e*u*a*> wrote:
> Mr Wise, > > Along with detecting erroneous data, are you able to tell us if we should also be prepared to find and drop rows with missing (blank) fields? > > All the best.
HI Zachary (and everyone), What the spec says is that rows with erroneous data need to dropped. In Assignment 1, the program needed to not proceed when an error had been detected, and instead print an error message. That is, the bad value was not printed. What I'm suggesting here is similar: if an error is found don't print the line on standard output, which has the effect of dropping it from further consideration by downstream programs. To keep error messages away from the good stuff, they should go to standard error. Fair enough? Cheers MichaelW

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