C programming · Lesson
Learn to distinguish a program that does not compile from one that compiles but produces the wrong result.
A compilation error prevents the program from starting; a logical error passes the compiler but violates the specification. Finding both requires diagnostics and targeted tests.
specification → reproduce the bug → inspect output/diagnostics → locate the line → fix → rerun the same test
Use Start and Step: when the active block changes, ConceptStep also highlights the C lines representing that same step.
Run C executes only the example shown on the left, using stdin on the right. The coding challenge below has a separate editor and test button.
1#include <stdio.h>
2
3int main(void)
4{
5 int voto;
6 scanf("%d", &voto);
7
8 if (voto >= 60)
9 printf("SUFFICIENTE\n");
10 else
11 printf("INSUFFICIENTE\n");
12
13 return 0;
14}
Fix the buggy program: score 60 passes. Read integer; print OK if >=60, otherwise NO.
This is a different program from lab 1. Complete the starter code: Check all test cases compiles this editor and tests every input, including boundary cases.
The specification says 60 is a pass. Which correction also makes boundary value 60 pass?
Challenge 1 / 5 · Understanding
Progress: 0 / 5 · correct: 0
ConceptStep separates what is required from what is recommended or useful as reinforcement. Only required prerequisites block your progress.
Relationships: solid line = required · dashed line = recommended · dotted line = reinforcement.