Got it! This site uses cookies. You consent to this by clicking on "Got it!" or by continuing to use this website.nbsp; Note: This appears on each machine/browser from which this site is accessed.
You are not logged in. Go to Login page. You need to login before you can view more content. (content omitted that requires login)to be added
5. Iteration without loops
6. Requirements
Write a C program to do the following.
Create a C program that reads in a non-negative integer representing how many pairs of nonnegative floating point approximation numbers, each representing a width and a height, respectively, of a square, follow. The program is to read in each pair, print the points and the area of that square. At most 4 pairs of points are in the data.
Make no unnecessary checks to see of the limit has been reached.
Do not use any looping features! There is a major point deduction for using any type of loop.
Note: At this time, we do not know enough to separate the repeated input, processing, and output.
FYI: This method is known as loop unrolling and is used in special cases to speed up certain code.
If the requirements are unclear in any way, use any provided input and output to resolve the discrepancy.
Domain knowledge is the background knowledge that is useful in solving a problem, designing a solution, implementing the solution, etc. The following domain knowledge may be useful for this requirement.
The area of a square is the width multiplied by the height.
Note: In addition to specific domain knowledge, you should be familiar with all concepts covered to this point in the course.
8. Coding notes
The following coding examples and/or notes may be of use for this requirement.
Make all necessary assumptions. Make no unnecessary assumptions.
In addition to specific coding examples, you should be familiar with all concepts covered to this point in the course.
9. Starter program
You are provided with the following starter program in file iteration.c.
Do not remove any comment that starts with three slashes.
Here is the C code.
You are to fill in the missing parts of the program according to the work requirements (see above).
In the comments at the top, you are to fill in the author (your name), help received (person and type of help), and pseudo-code parts which are not in the solution (usually provided, but you need to add them). Remove the parentheses too.
10. Possible solution
Begin solution
Here is a possible solution to the above problem. Note: Once a solution is provided, or the day before the next class, further submissions for this work receive no credit.
End solution
11. Examples of input and output
Here are some examples of input and output for the above program code.
Here is an example input from file input1.txt.
For the above example input, here is the expected output.
Here is an example input from file input2.txt.
For the above example input, here is the expected output.
Here is an example input from file input3.txt.
For the above example input, here is the expected output.
Here is an example input from file input4.txt.
For the above example input, here is the expected output.
12. Pseudo-code
Pseudo-code is a "false" code. It is not really code, but a simplified English explanation that is somewhat similar to code. Pseudo-code is useful for understanding what a program does. For this work, the following can be used as the pseudo-code. Adjust if needed.
Note: Only some essential details are included. Some details, such as input, prompts, input echo, and obviously needed output are omitted.
The best way to copy-paste pseudo-code that includes indented code (e.g., with tabs) is as follows (in the code file) using a multi-line comment.
/*
(pasted pseudo-code here)
*/
13. Processing
It is best to separate input, processing and output into different parts of a program.
Since C has limited string handling capabilities (they can get complex), some processing involving string processing is moved to the output section of the code.
14. Scoring rubric
CS 101 - L5 : Lab#5: Iteration without loops
Your grade: _ / 20
[LATE] Late or redo penalty: _ / -20
[SUBMIT] Not submitted properly: _ / -20
[RUN] Does not compile, run-time crash, etc.: _ / -20
[ETHICS] Ethical issues: _ / -20
[HEADER] Header comments not done as required: _ / -10
[STYLE] Inconsistant style or indentation: _ / -10
[CODE] Code guidelines ignored: _ / -20
[XCODE] Code used not yet covered: _ / -10
[REMOVED] Triple slash comments removed: _ / -10
[ADDED] Code added outside of marked areas: _ / -10
[OUTPUT] Functional requirements met: _ / 20
[CREDIT] Extra credit: _ / +4
Comments: