9 lines
1.4 KiB
HTML
9 lines
1.4 KiB
HTML
<!doctype html><html lang="en"><meta charset="utf-8"><title>Values and decisions</title><h1>Values and decisions</h1><p>15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.</p><p>A decision chooses which statements run. The policy here is “ready at 80 or higher.” Trace 85, 79, 80, and 81 before running each case. The comparison includes 80. A program that prints the right answer for 85 may still be wrong at the boundary. Add a separate check rejecting scores below 0 or above 100; rejection and needing practice mean different things.</p><p>C begins at <code>main</code>. <code>stdio.h</code> declares output functions; <code>puts</code> adds a newline. Semicolons terminate statements. An integer and a pointer are different kinds of value.</p><pre><code class="language-c">#include <stdio.h>
|
|
#include <assert.h>
|
|
|
|
int main(void) {
|
|
int score = 85;
|
|
if (score >= 80) puts("Ready"); else puts("Practice");
|
|
return 0;
|
|
}
|
|
</code></pre><p><strong>Expected result:</strong> <code>Ready</code></p><h3>Practice and evidence</h3><p>Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.</p><p><a href="https://gcc.gnu.org/onlinedocs/gcc/Standards.html">Language reference</a></p></html> |