Skip to content

Commit c8edd87

Browse files
authored
Merge pull request #4420 from X0RW3LL/patch-1
Minor styling fixes
2 parents 8e93328 + c3997a6 commit c8edd87

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/c-language/name-spaces.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,19 +14,19 @@ The compiler sets up "name spaces" to distinguish between the identifiers used f
1414
1515
This list describes the name spaces used in C.
1616

17-
Statement labels
17+
**Statement labels**\
1818
Named statement labels are part of statements. Definitions of statement labels are always followed by a colon but are not part of **`case`** labels. Uses of statement labels always immediately follow the keyword **`goto`**. Statement labels do not have to be distinct from other names or from label names in other functions.
1919

20-
Structure, union, and enumeration tags
20+
**Structure, union, and enumeration tags**\
2121
These tags are part of structure, union, and enumeration type specifiers and, if present, always immediately follow the reserved words **`struct`**, **`union`**, or **`enum`**. The tag names must be distinct from all other structure, enumeration, or union tags with the same visibility.
2222

23-
Members of structures or unions
23+
**Members of structures or unions**\
2424
Member names are allocated in name spaces associated with each structure and union type. That is, the same identifier can be a component name in any number of structures or unions at the same time. Definitions of component names always occur within structure or union type specifiers. Uses of component names always immediately follow the member-selection operators (**->** and **.**). The name of a member must be unique within the structure or union, but it does not have to be distinct from other names in the program, including the names of members of different structures and unions, or the name of the structure itself.
2525

26-
Ordinary identifiers
26+
**Ordinary identifiers**\
2727
All other names fall into a name space that includes variables, functions (including formal parameters and local variables), and enumeration constants. Identifier names have nested visibility, so you can redefine them within blocks.
2828

29-
Typedef names
29+
**Typedef names**\
3030
Typedef names cannot be used as identifiers in the same scope.
3131

3232
For example, since structure tags, structure members, and variable names are in three different name spaces, the three items named `student` in this example do not conflict. The context of each item allows correct interpretation of each occurrence of `student` in the program. (For information about structures, see [Structure Declarations](../c-language/structure-declarations.md).)

0 commit comments

Comments
 (0)