Soloway's recurring rainfall: Difference between revisions

m
no edit summary
m (Thundergnat moved page Soloway's Recurring Rainfall to Soloway's recurring rainfall: captalization policy (why is it so hard for people to follow this?))
mNo edit summary
Line 14:
* For languages where the user is inputting data, the number of data inputs can be "infinite"
* A complete implementation should handle error cases reasonably (asking the user for more input, skipping the bad value when encountered, etc)
 
The purpose of this problem, as originally proposed in the 1980's through it's continued use today, is to just show fundamentals of CS: iteration, branching, program structure, termination, management of data types, input/output (where applicable), etc with things like input validation or management of numerical limits being more "advanced". It isn't meant to literally be a rainfall calculator so implementations should strive to implement the solution clearly and simply.
 
'''References:'''
6

edits