Files

T

Antigravity Agent e9cbf23ab5 docs(10_Wiki): Dev 폴더 누락분 반영 — Topic_Programming으로 통합

이전 재구성 작업에서 Dev/ 폴더가 누락되었던 것을 반영.

- Dev/Topic_Programming(중첩 폴더, 78개)은 Dev 자체 최상위 폴더들
  (Architecture/Conventions/Engineering_Intelligence 등)과 완전 중복이라 제거.
- Dev 최상위 엔지니어링 지식 폴더(Architecture/Conventions/Engineering_Intelligence/
  Failure_Library/Generalized_Principles/Language/Pattern_Catalog/Platform_Guides/
  Subsystems, 77개)는 이미 Topic_Programming/Topic_Programming에 더 최신 버전이
  존재해 중복 제거(고유 콘텐츠 1개는 예외 처리하여 이동 보존).
- Dev의 W3Schools 언어 튜토리얼 폴더(Topic_C/CPP/CSS/CSharp/HOWTO/HTML/Java/
  JavaScript/PHP/Python/SQL/W3CSS, 1201개)는 전부 Topic_Programming 하위로 이동.
- 에이전트 운영 상태(.astra/docs)는 그대로 유지, 콘텐츠 폴더만 정리.
- Topic_Programming 최종 문서 수: 2784 → 3985.

2026-07-05 00:39:13 +09:00

3.3 KiB

Raw Blame History

id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit

title

Java Errors

🎯 한 줄 통찰 (One-line insight)

Logical errors are explicitly called "hardest to find" because the program compiles AND runs without crashing — it just produces wrong results (e.g., x - y instead of x + y), meaning no error message points you to the bug; only testing against expected output reveals it. [S1]

🧠 핵심 개념 (Core concepts)

Compile-time error — detected by the compiler, prevents the code from running (syntax/type issues). [S1]
Runtime error — occurs while running, often causes crashes (e.g., division by zero, out-of-bounds access). [S1]
Logical error — code runs and produces output, but the output is wrong; hardest category to detect. [S1]
Good habits — meaningful variable names, reading error messages for line numbers, checking for missing semicolons/braces, watching for typos. [S1]

📖 세부 내용 (Details)

Missing semicolon: int x = 5 System.out.println(x); // error: ';' expected. [S1]
Undeclared variable: System.out.println(myVar); // cannot find symbol: variable myVar. [S1]
Mismatched types: int x = "Hello"; // incompatible types: String cannot be converted to int. [S1]
Division by zero: int x = 10; int y = 0; int result = x / y; // ArithmeticException: / by zero. [S1]
Array out of bounds: int[] numbers = {1, 2, 3}; System.out.println(numbers[8]); // ArrayIndexOutOfBoundsException. [S1]
Logical error: int sum = x - y; when addition was intended — no exception thrown, just wrong output. [S1]

⚖️ 모순 및 업데이트 (Contradictions & updates)

소스에서 모순되는 정보는 발견되지 않음.

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — 세 가지 에러 유형 분류는 이후 디버깅/예외 처리 챕터의 기초 개념이다. [S1]

💻 코드 패턴 (Code patterns)

Logical error — code runs but result is wrong (Java):

int x = 10;
int y = 2;
int sum = x - y;  // mistakenly subtracts instead of adds
System.out.println("x + y = " + sum);  // "x + y = 8" (expected 12)

✅ 검증 상태 및 신뢰도

상태: draft
검증 단계: conceptual
출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
신뢰 점수: 0.90
중복 검사 결과: 신규 생성 (New discovery)

🔗 지식 그래프 (Knowledge Graph)

상위/루트: Java Tutorial
관련 개념: Java Debugging, Java Try Catch
참조 맥락: 에러 유형 분류(컴파일/런타임/논리) — 디버깅 챕터로 직접 이어짐.

📚 출처 (Sources)

[S1] W3Schools — Java Errors — https://www.w3schools.com/java/java_errors.asp

📝 변경 이력 (Change history)

2026-07-04: Initial draft synthesized from the W3Schools "Java Errors" page (Astra wiki-curation, P-Reinforce v3.1 format).

3.3 KiB Raw Blame History