2nd/10_Wiki/Topics/Domain_Programming/Topic_CSharp/CSharp_OOP.md

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
csharp-oop	C# - What is OOP?	Programming_Language	draft	conceptual		object-oriented programming C# DRY principle C# OOP 소개		B	0.83	2026-07-04	2026-07-04			csharp programming-language w3schools oop	https://www.w3schools.com/cs/cs_oop.php

CSharp OOP

🎯 한 줄 통찰 (One-line insight)

Unlike Topic_C, which never had an OOP chapter at all (procedural only), and Topic_CPP, where OOP was introduced as an OPTIONAL paradigm layered on top of C-style procedural code, this C# chapter frames OOP as the language's core identity from the very first sentence — reinforcing what the Syntax chapter already forced structurally (every line of code must be inside a class): in C#, object-oriented isn't an available style choice the way it was for C++, it's the only way the language works. [S1]

🧠 핵심 개념 (Core concepts)

• Procedural vs. object-oriented — procedural programming writes procedures/methods that operate on data; OOP creates objects that bundle BOTH data and methods together. [S1]
• Claimed OOP advantages — faster/easier to execute, clearer program structure, supports the DRY principle (Don't Repeat Yourself), enables reusable applications with less code and shorter development time. [S1]
• DRY principle — extract code common to the application into a single place and reuse it, instead of repeating it. [S1]
• Class — a template/blueprint for creating objects. [S1]
• Object — an instance of a class; created objects inherit all variables and methods from their class. [S1]
• Class-vs-object illustration — Fruit (class) → Apple, Banana, Mango (objects); Car (class) → Volvo, Audi, Toyota (objects). [S1]

📖 세부 내용 (Details)

• No code examples in this chapter — purely conceptual, deferring class/object syntax to the next chapter. [S1]

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

• OOP가 선택이 아니라 언어의 본질로 제시됨: Topic_C에는 OOP 챕터 자체가 없었고(순수 절차적 언어), Topic_CPP는 OOP를 C 스타일 절차적 코드 위에 선택적으로 얹는 패러다임으로 소개했지만, C#은 Syntax 챕터에서 이미 확인된 "모든 코드는 class 안에" 구조적 강제를 그대로 반영해 OOP를 언어의 유일한 작동 방식으로 첫 문장부터 제시한다는 점이 확인됨. [S1]

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — Fruit/Car를 class로, 그 인스턴스들을 object로 비유하는 개념 설명이 원문에서 제시됨. [S1]

💻 코드 패턴 (Code patterns)

없음 — 이 챕터는 코드 예제가 없는 개념 소개 챕터.

✅ 검증 상태 및 신뢰도

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

🔗 지식 그래프 (Knowledge Graph)

• 상위/루트: C# Tutorial
• 관련 개념: CSharp Method Parameters Return, CSharp Classes, CPP OOP
• 참조 맥락: OOP Basics 섹션 — Classes and Objects 챕터로 이어짐.

📚 출처 (Sources)

• [S1] W3Schools — C# - What is OOP? — https://www.w3schools.com/cs/cs_oop.php

📝 변경 이력 (Change history)

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