CPSC 421-010 Object-Oriented Programming Spring 2026

If you did not take the Exercise 8: For Statement Quiz nor do Exercise 17: For Semantics I, then you cannot do this exercise, as it is based on your work on the quiz.

In your for semantics repository is a file ForSemantics.cpp. It has a set of separate test cases with some setup, the code to evaluate, and an answer checked via an assert(), e.g.,

Each test case is in its own block statement to isolate its scope. The test cases are scenarios of using the original code from the quiz, followed by a test case with your individual answers. There are multiple scenarios for each example/answer from the quiz.

One special case is for Q3, which gave you macros (e.g., INCR) instead of the actual code. For that one, we used the preprocessing #define to make them into statements.

This is a non-standard use of preprocessing statements, so don't treat it as a general solution.

A CMake configuration is provided. So use the standard procedure to configure and build. There is no target run provided in the Makefile, so you will have to run the test program on the command line.

So your job is to:

• Fix the indentation in a single commit. Depending on how you entered the code in the quiz, it might not have proper indentation after it is injected. Do this in a single commit.
• Fix any naming in a single commit. Some of you decided to rename the loop-control variable. Since it was i in the original for-loop, it should be i in the semantically-equivalent while-loop. Not count, vCount, or q. Besides, i is the standard name for a counter in a loop.
• Replace any declaration statements with multiple declarations into separate declarations, e.g., change int total = 0, i = 0;
• Fix the compile errors one-by-one with a separate commit for each test case. All of the test cases that use the original for-loop will pass, so the compile errors are because your while-loops are not semantically equivalent to the original for-loop. This tends to be a variable scope problem.
• Once the compiler errors are fixed, you need to see if the test cases pass. Run the program and fix the code so that the assertions pass. Commit one fix at a time. As with the compiler errors, the assertion errors are because your while-loops are not semantically equivalent to the for-loops. Note that once an assertion fails, your program stops. So you will end up fixing this from top to bottom.

You can only change what is between the // @START and // @END comments. Changes to any other places in the code will result in a 0 on the exercise.