Grading Guidelines for hw4
==============================================================
Problem 1. 30 points

0 credit if they did it all in the main function, without writing 
a function ComputePay.  

No need to check if the user entered 'y' or 'n' in response to the the
"Is today a weekday?" question.  Also no need to check for negative
numbers.

It's okay if they made the program loop, always asking for
another wage/hours/boolean, or if it just does one case and then stops.

partial credit as you see fit - try it on a few cases.
==============================================================
Problem 2. 30 points

0 credit if they did it all within the main function, without writing
the function HasEvenDigit().  It was suggested that they model it based
on the program 4-5 in the book (as the sample solution does), but it's 
okay if they did it some other way, as long as the function is there.

It's okay if they made the program loop, always asking for
another number, or if it just does one and then stops.

partial credit as you see fit - try it on a few cases.  All 
test cases should be done with numbers without 0.  The problem
was not properly defined to handle such cases, so just use numbers
like 1234, 4345, etc.  There's of course a C-imposed limit on how big
the numbers can be, and that's okay.


==============================================================
Problem 3. 40 points

The basic functionality should still be correct, so no need to 
check the workings of the details of the code, since
it was already checked in hw3.  However, 10 points off if they
didn't use the version of the code with an enumerated type, since
we told them to use the one from hw3, problem 3.  It's okay if they
used either the switch statement or cascaded if.

-30 points if the code does not use the three different functions
they were told to write.  -10 for each function not included.

Otherwise, partial credit as you see fit.