Comparing values

Coin Quest must ask whether a goal was reached, whether two item names match, or whether time remains before deciding what happens.

A comparison asks a question and produces a boolean. == asks whether values are equal; ~= asks whether they differ.

The ordered operators <, >, <=, and >= compare numbers. A single = assigns and is not an equality question.

--!strict asks Studio to check your code for type mistakes. It is an instruction for the editor and produces no Output message.

print(...) calls the built-in print function. Put the values to show inside its parentheses; separate multiple values with commas. Read the result in Studio's Output panel.

local is read as “local”: it creates a name that is available only in the current code scope.

= is read as “is assigned”: it evaluates the right side and stores that value in the name on the left.

Read one statement at a time: name the value being read, what the operation does, and where its result goes. Keep identifiers exactly as written so you can find them again in the code.

Pause at calls, conditions, and loops. Explain when the body runs before moving to the next statement; use the line notes above when a symbol is unfamiliar.

Begin at the first executable statement. Comments and blank lines do not run; a branch chooses which block runs, and a loop may revisit its body.

Line 3: coins is the current amount.

Line 4: target is the required amount.

Line 5: >= includes values equal to or greater than the target.

Line 6: < checks whether the current amount is lower.

Line 8: The two boolean results are printed.

Before running, identify the starting values and any existing Studio objects this example needs. List what you expect to change.

After your practice change, check this result: Each comparison produces the boolean you predicted at the boundary value.

Reading or printing a value leaves it unchanged. Look for assignments, calls that change state, and property updates to explain each change you observe.