This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
haas:spring2017:cprog:projects:dow0 [2015/09/13 15:12] – external edit 127.0.0.1 | haas:spring2017:cprog:projects:dow0 [2017/01/31 20:14] (current) – [Submission] wedge | ||
---|---|---|---|
Line 122: | Line 122: | ||
<cli> | <cli> | ||
- | lab46: | + | lab46: |
Which year: 2014 | Which year: 2014 | ||
January 1st, 2014 falls on: Wednesday | January 1st, 2014 falls on: Wednesday | ||
- | lab46: | + | lab46: |
</ | </ | ||
The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate. | The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate. | ||
+ | ====Output Specifications==== | ||
+ | Your program must output as follows: | ||
+ | |||
+ | * Input prompts, and everything else except the actual day of the week should be output to STDERR | ||
+ | * The calculated day of the week needs to be displayed to STDOUT | ||
+ | * The output MUST contain the " | ||
+ | * YEAR must be all 4 digits, exactly as input by the user | ||
+ | * The calculated day of the week must be fully spelled out and correct, with the first letter capitalized, | ||
=====Reflection===== | =====Reflection===== | ||
- | Be sure to provide any commentary on your opus regarding realizations had and discoveries made during your pursuit of this project. | + | Be sure to provide any commentary on your journal |
- | * 2000 by definition isn't a leap year, but how does this algorithm work for 2000 in general? | ||
* Try this algorithm on some years in the 20th century and see how it fares. | * Try this algorithm on some years in the 20th century and see how it fares. | ||
* Is it correct? Is it correct for any of them? | * Is it correct? Is it correct for any of them? | ||
Line 145: | Line 152: | ||
* Executed program must display a total of 2 lines, one for input, one for output. | * Executed program must display a total of 2 lines, one for input, one for output. | ||
* Input **must** be in the form of a complete (i.e. four-digit) year | * Input **must** be in the form of a complete (i.e. four-digit) year | ||
+ | * input must be a number, NOT a string | ||
* Output must be correct, and match the form given in the sample output above. | * Output must be correct, and match the form given in the sample output above. | ||
* Code must be nicely and consistently indented (you may use the **indent** tool) | * Code must be nicely and consistently indented (you may use the **indent** tool) | ||
* Code must be commented | * Code must be commented | ||
- | * have a properly filled-out comment banner at the top | ||
- | * have at least 20% of your program consist of **< | ||
* Output Formatting (including spacing) of program must conform to the provided output (see above). | * Output Formatting (including spacing) of program must conform to the provided output (see above). | ||
* Track/ | * Track/ | ||
Line 157: | Line 163: | ||
<cli> | <cli> | ||
- | $ submit cprog dow0 dayofweek.c | + | $ submit cprog dow0 dow0.c |
Submitting cprog project " | Submitting cprog project " | ||
- | -> dayofweek.c(OK) | + | -> dow0.c(OK) |
SUCCESSFULLY SUBMITTED | SUCCESSFULLY SUBMITTED | ||
Line 165: | Line 171: | ||
You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. | You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. | ||
+ | |||
+ | What I'll be looking for: | ||
+ | |||
+ | < | ||
+ | 52: | ||
+ | *:dow0:data stored and calculated pursuant to algorithm and specifications [4/4] | ||
+ | *:dow0:code is pushed to lab46 repository [4/4] | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *:dow0:no negative compiler messages for dow0.c [4/4] | ||
+ | </ | ||