docs(10_Wiki): 위키 구조 정리 — 언어 튜토리얼 카테고리 폴더 제거 + 신규 자산 동기화

Topic_CSS/Topic_HTML/Topic_JavaScript/Topic_Prompt/Topic_Comfyui 등 기존 카테고리 폴더를 정리하고, Topic_Graphic/Dev 등 신규 산출물과 Topics 내부 세션/메모리 기록을 동기화.
2026-07-05 00:10:59 +09:00
parent a397bc4720
commit 1cfd3bbb56
1495 changed files with 68534 additions and 27 deletions
@@ -0,0 +1,71 @@
+---
+id: c-memory-management
+title: "C Memory Management"
+category: "Programming_Language"
+status: "draft"
+verification_status: "conceptual"
+canonical_id: ""
+aliases: ["memory management overview", "C 메모리 관리"]
+duplicate_of: ""
+source_trust_level: "B"
+confidence_score: 0.85
+created_at: 2026-07-04
+updated_at: 2026-07-04
+review_reason: ""
+merge_history: []
+tags: ["c", "programming-language", "w3schools", "memory-management"]
+raw_sources: ["https://www.w3schools.com/c/c_memory_management.php"]
+applied_in: []
+github_commit: ""
+---
+
+# [[C Memory Management]]
+
+## 🎯 한 줄 통찰 (One-line insight)
+Manual memory management is presented as a genuine TRADE, not a burden imposed for no reason — the source frames it explicitly as "complicated... but also quite powerful when used correctly," meaning C hands the programmer full responsibility for allocation/deallocation specifically because that same responsibility is what enables performance optimization impossible in languages with automatic garbage collection. [S1]
+
+## 🧠 핵심 개념 (Core concepts)
+- **Memory management** — the process of controlling how much memory a program uses, via three operations: allocation, reallocation, and deallocation ("freeing"). [S1]
+- **Automatic sizing for basic variables** — C automatically reserves the correct byte size for `int`/`float`/`double`/`char` variables; `sizeof` reveals these sizes (4/4/8/1 bytes respectively). [S1]
+- **Manual responsibility** — unlike some languages, C requires the PROGRAMMER to manage memory explicitly, which is more error-prone but enables finer performance control. [S1]
+- **Pointers as the memory-management tool** — since dynamic memory is only reachable via pointers, memory management is inherently pointer-based work. [S1]
+
+## 📖 세부 내용 (Details)
+- Confirming basic type sizes via sizeof: `int myInt; float myFloat; double myDouble; char myChar; printf("%zu\n", sizeof(myInt)); // 4 printf("%zu\n", sizeof(myDouble)); // 8`. [S1]
+
+## ⚖️ 모순 및 업데이트 (Contradictions & updates)
+- **수동 메모리 관리는 강력함과 위험의 트레이드오프**: 복잡하지만 제대로 사용하면 매우 강력하다는 점, 그리고 포인터를 다룰 때는 다른 메모리 주소의 데이터를 손상시킬 위험이 있으니 주의해야 한다는 점이 함께 강조됨. [S1]
+
+## 🛠️ 적용 사례 (Applied in summary)
+현재 발견된 실제 적용 사례가 없습니다 — 이 챕터가 개관하는 할당/재할당/해제 세 가지 개념이 다음 챕터들(Memory Allocate/Reallocate/Deallocate)에서 각각 상세히 다뤄지는 로드맵 역할을 한다. [S1]
+
+## 💻 코드 패턴 (Code patterns)
+Checking the actual byte sizes of C's basic types with sizeof (C):
+```c
+int myInt;
+float myFloat;
+double myDouble;
+char myChar;
+printf("%zu\n", sizeof(myInt));    // 4 bytes
+printf("%zu\n", sizeof(myFloat));  // 4 bytes
+printf("%zu\n", sizeof(myDouble)); // 8 bytes
+printf("%zu\n", sizeof(myChar));   // 1 byte
+```
+
+## ✅ 검증 상태 및 신뢰도
+- **상태:** draft
+- **검증 단계:** conceptual
+- **출처 신뢰도:** B (W3Schools — widely used educational reference, not a primary standards body)
+- **신뢰 점수:** 0.85
+- **중복 검사 결과:** 신규 생성 (New discovery)
+
+## 🔗 지식 그래프 (Knowledge Graph)
+- **상위/루트:** [[C Tutorial]]
+- **관련 개념:** [[C Memory Access]], [[C Memory Allocate]]
+- **참조 맥락:** 메모리 관리 개관 — 메모리 할당(Memory Allocate) 챕터로 이어짐.
+
+## 📚 출처 (Sources)
+- [S1] W3Schools — C Memory Management — https://www.w3schools.com/c/c_memory_management.php
+
+## 📝 변경 이력 (Change history)
+- 2026-07-04: Initial draft synthesized from the W3Schools "C Memory Management" page (Astra wiki-curation, P-Reinforce v3.1 format).