컴파일 오류와 읽는 방법

When you press Verify, the IDE checks your code first. If something is wrong, a compile error appears in red. It is helping, not scolding. 🙂

The IDE turns your sketch into machine code before uploading. This step is called compiling, and it catches mistakes early.

Errors can cascade, so always fix the first one listed. Later errors often vanish once the top problem is solved.

Each message names a line number where trouble was spotted. Jump to that line first, then check the one just above it.

The most common error is a forgotten semicolon. Every statement needs one, so add the missing semicolon to end the line.

Every opening brace needs a matching close. A leftover or missing brace confuses the compiler about where a block ends.

This message means a name was used but never defined, often a typo. Check the spelling, since Arduino is case-sensitive.

Functions expect a set number of values in their parentheses. Too few or too many triggers an argument error.

HIGH and high are not the same to the compiler. A tiny capitalization slip can stop your whole sketch from building.

An error stops the build entirely. A warning is just advice and still lets you upload, though it is worth a look.

Change one thing, then press Verify to recompile. Working in small steps makes it clear which fix actually solved the problem.

Let's check your error-reading strategy.

You learned that compiling catches mistakes, to read the first error and its line, and that semicolons, braces, and typos cause most of them. 🎉