e9cbf23ab5
이전 재구성 작업에서 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.
3.0 KiB
3.0 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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| c-conditions-else | C Else | Programming_Language | draft | conceptual |
|
B | 0.84 | 2026-07-04 | 2026-07-04 |
|
|
C Else
🎯 한 줄 통찰 (One-line insight)
Naming a boolean condition variable descriptively (isDay instead of a raw time < 18 expression) doesn't change the program's behavior at all — it's purely a communication device for future readers — and the source explicitly frames this as its entire justification: "makes it easy to understand what the condition means," not a performance or correctness improvement. [S1]
🧠 핵심 개념 (Core concepts)
else— runs a block of code when the pairedifcondition is false; there is no separate condition to check forelseitself. [S1]- Mutually exclusive branches — exactly one of the
iforelseblock executes, never both, never neither. [S1] - Descriptive boolean naming — storing a condition in a variable like
isDaydocuments the condition's MEANING, not just its mechanics. [S1]
📖 세부 내용 (Details)
- Basic if/else:
int time = 20; if (time < 18) { printf("Good day."); } else { printf("Good evening."); } // Outputs "Good evening.". [S1] - Same logic with a descriptively-named boolean:
bool isDay = time < 18; if (isDay) { printf("Good day."); } else { printf("Good evening."); }. [S1]
⚖️ 모순 및 업데이트 (Contradictions & updates)
- 현재까지 발견된 모순 사항 없음 (No contradictions found in available sources).
🛠️ 적용 사례 (Applied in summary)
시간(time)이 18보다 작은지에 따라 "좋은 하루"/"좋은 저녁"을 출력하는 예제가 원문에서 직접 실전 활용 사례로 제시됨(시간대 기반 인사말 로직). [S1]
💻 코드 패턴 (Code patterns)
Naming a boolean condition descriptively for readability (C):
int time = 20;
bool isDay = time < 18;
if (isDay) {
printf("Good day.");
} else {
printf("Good evening.");
}
✅ 검증 상태 및 신뢰도
- 상태: draft
- 검증 단계: conceptual
- 출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
- 신뢰 점수: 0.84
- 중복 검사 결과: 신규 생성 (New discovery)
🔗 지식 그래프 (Knowledge Graph)
- 상위/루트: C Tutorial
- 관련 개념: C Conditions, C Conditions ElseIf
- 참조 맥락: else 문 — else if 문(Conditions ElseIf) 챕터로 이어짐.
📚 출처 (Sources)
- [S1] W3Schools — C Else — https://www.w3schools.com/c/c_conditions_else.php
📝 변경 이력 (Change history)
- 2026-07-04: Initial draft synthesized from the W3Schools "C Else" page (Astra wiki-curation, P-Reinforce v3.1 format).