From 4019930bf7c03cb07d6ad284a9754a12e4c29c3f Mon Sep 17 00:00:00 2001 From: Richard Stallman Date: Thu, 1 Feb 2024 21:53:00 -0500 Subject: [PATCH] * c.texi: (Unions, Structures): Unions are compond types too. --- ChangeLog | 1 + c.texi | 8 +++++--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 2467c92..9de42de 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,7 @@ 2024-02-01 Richard Stallman * c.texi: Specify @codequoteundirected on and @codequotebacktick on. + (Unions, Structures): Unions are also compond types. 2024-01-30 Richard Stallman diff --git a/c.texi b/c.texi index f47b642..753ee4d 100644 --- a/c.texi +++ b/c.texi @@ -5867,8 +5867,8 @@ appropriate unsigned integer type. A @dfn{structure} is a user-defined data type that holds various @dfn{fields} of data. Each field has a name and a data type specified in the structure's definition. Because a structure combines various -fields, each of its own type, we call a structure type a -@dfn{compound type}. +fields, each of its own type, we call a structure type a @dfn{compound +type}. (Union types are also compound types; @pxef{Unions}.) Here we define a structure suitable for storing a linked list of integers. Each list item will hold one integer, plus a pointer @@ -6646,7 +6646,9 @@ assignment would be invalid because the left operand is not an lvalue. A @dfn{union type} defines alternative ways of looking at the same piece of memory. Each alternative view is defined with a data type, -and identified by a name. A union definition looks like this: +and identified by a name. Because a union combines various types, it +is considered a @dfn{compound type}, like structures +(@pxref{Structures}). A union definition looks like this: @example union @var{name}