Naming policy
A naming policy is a consistent set of rules for choosing names for program entities.
Modern C, Third Edition
A naming policy is a consistent set of rules for choosing names for program entities.
- How it is used
- Sets consistent rules for choosing identifiers while separating technical restrictions from semantic conventions.
- How deep it goes
- Defines identifier categories, namespace hazards, and reserved-name patterns; stops short of listing every restriction.
- Examples
- Uses C declarations, confusing identifier pairs, and alternative names to demonstrate collision avoidance and distinguishability.
- What you can do after
- Apply it by choosing consistent, conforming identifiers, especially in declarations visible through header files.
Modern C
A naming policy is a consistent set of rules governing how program identifiers are formed and selected.
- How it is used
- Governs identifier formation and selection while reducing collisions across headers, macros, libraries, and global interfaces.
- How deep it goes
- Defines technical restrictions and semantic conventions, then applies selected C rules without cataloguing every reserved identifier.
- Examples
- Uses memory_sum declarations, collision-prone names, and a table comparing recognizable and distinguishable identifiers.
- What you can do after
- Practice/perform consistent C identifier selection, header hygiene, reserved-name avoidance, and limited interface exposure.
Related concepts
- identifierconfigures · An identifier is a name or value that denotes or distinguishes an entity or program element within a system.
- camel caseincludes · Camel case is a naming convention that joins words without separators and marks word boundaries with internal capitalization, typically leaving the first word lowercase.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.