Files
2nd/10_Wiki/Dev/Topic_CSharp/CSharp_Variables_Identifiers.md
T
Antigravity Agent 1cfd3bbb56 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

3.5 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
csharp-variables-identifiers C# Identifiers Programming_Language draft conceptual
variable naming rules C#
C# 식별자
B 0.83 2026-07-04 2026-07-04
csharp
programming-language
w3schools
identifiers
naming
https://www.w3schools.com/cs/cs_variables_identifiers.php

CSharp Identifiers

🎯 한 줄 통찰 (One-line insight)

C#'s identifier rules (letters/digits/underscore, must start with letter/underscore, case-sensitive, no reserved words) are the same rule-set every C-family language in this series has used verbatim — the interesting detail isn't the rule itself but the STYLE convention layered on top: C# explicitly recommends lowercase-starting names (camelCase, e.g. minutesPerHour), which will matter later when C#'s method/class names are shown starting with an UPPERCASE letter (PascalCase) — a naming-convention split by identifier kind that C and C++ never enforced this explicitly. [S1]

🧠 핵심 개념 (Core concepts)

  • Identifier — the unique name given to a variable. [S1]
  • Character rules — letters, digits, and underscore (_) allowed; must begin with a letter or underscore (never a digit). [S1]
  • Case sensitivitymyVar and myvar are distinct variables. [S1]
  • No whitespace — names cannot contain spaces. [S1]
  • No reserved words — C# keywords like int or double cannot be used as identifier names. [S1]
  • Style convention (recommended, not enforced) — start with a lowercase letter; prefer descriptive names (minutesPerHour) over terse ones (m) for readability and maintainability. [S1]

📖 세부 내용 (Details)

  • Good vs. acceptable naming contrast: int minutesPerHour = 60; // Good vs int m = 60; // OK, but not so easy to understand. [S1]

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

  • 명명 규칙 자체는 C/C++/Java와 동일: 문자/숫자/언더스코어, 숫자로 시작 불가, 대소문자 구분, 예약어 사용 불가라는 규칙이 이전 언어들과 동일함이 확인됨 — 차이는 규칙이 아니라 스타일 권장(lowercase 시작, 서술적 이름 선호)에 있음. [S1]

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — minutesPerHour vs m 이름 비교가 원문에서 스타일 예제로 제시됨. [S1]

💻 코드 패턴 (Code patterns)

Descriptive vs. terse identifier naming (C#):

// Good
int minutesPerHour = 60;
// OK, but not so easy to understand what m actually is
int m = 60;

검증 상태 및 신뢰도

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

🔗 지식 그래프 (Knowledge Graph)

📚 출처 (Sources)

📝 변경 이력 (Change history)

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