Files
2nd/10_Wiki/Topics/Topic_Programming/Topic_CPP/CPP_OOP.md
T
Antigravity Agent 9a135bd19d docs(10_Wiki): Topic_Business/General/Graphic/Programming을 Topics/ 하위로 이동
최상위 10_Wiki/Topic_*였던 4개 카테고리 폴더를 10_Wiki/Topics/Topic_* 로 재배치.
콘텐츠 변경 없음(순수 폴더 이동) — Topics/ 하위 나머지 폴더는 이미 지난 커밋에서
전부 정리된 상태(잔존 항목은 에이전트 운영 상태 및 사용자가 보존을 요청한
업데이트0615/무제 3.canvas 뿐).
2026-07-05 00:44:01 +09:00

3.3 KiB

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
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
cpp-oop C++ OOP Programming_Language draft conceptual
object-oriented programming
DRY principle
procedural vs OOP
C++ 객체지향 프로그래밍
B 0.85 2026-07-04 2026-07-04
cpp
programming-language
w3schools
oop
https://www.w3schools.com/cpp/cpp_oop.asp

C++ OOP

🎯 한 줄 통찰 (One-line insight)

The single-sentence distinction the source draws between procedural and object-oriented programming is organizational, not functional — procedural code is "organized around FUNCTIONS," OOP code is "organized around OBJECTS" that BUNDLE data and functions together — meaning the shift to OOP throughout this section of the tutorial isn't introducing new capabilities C++ lacked before, but reorganizing the SAME capabilities (variables, functions) around a different unit of grouping. [S1]

🧠 핵심 개념 (Core concepts)

  • OOP (Object-Oriented Programming) — organizing code around "objects" that hold both data and functions operating on that data. [S1]
  • Class vs. object — a class defines what an object should look like (a template); an object is created FROM a class and inherits its variables/functions. [S1]
  • DRY principle — "Don't Repeat Yourself"; move repeated code into functions or classes and reuse it. [S1]
  • OOP advantages — clearer program structure, easier maintenance/reuse/debugging, DRY-friendly, enables building full reusable applications faster. [S1]
  • Procedural vs. OOP — procedural organizes code around FUNCTIONS operating on data; OOP organizes code around OBJECTS that contain both data and functions together. [S1]

📖 세부 내용 (Details)

  • The Class → Objects mapping example: Fruit class → Apple/Banana/Mango objects; Car class → Volvo/Audi/Toyota objects. [S1]

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

  • 현재까지 발견된 모순 사항 없음 (No contradictions found in available sources).

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — 이 챕터의 클래스-객체 개념 개관이 다음 챕터(Classes and Objects)의 실전 코드로 바로 이어진다. [S1]

💻 코드 패턴 (Code patterns)

None — this is a conceptual overview page with no standalone code example.

검증 상태 및 신뢰도

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

🔗 지식 그래프 (Knowledge Graph)

📚 출처 (Sources)

📝 변경 이력 (Change history)

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