The
CCHARW_MAX symbol is specific to
ncurses.
X/Open Curses does not provide details for the layout of the
cchar_t
structure.
It tells what data are stored in it:
|
»
|
a spacing character (wchar_t, i.e., 32-bits).
|
|
»
|
non-spacing characters (again, wchar_t's).
|
|
»
|
attributes (at least 16 bits, inferred from the various ACS- and WACS-flags).
|
|
»
|
color pair (at least 16 bits, inferred from the unsigned short type).
|
The non-spacing characters are optional,
in the sense that zero or more may be stored in a
cchar_t.
XOpen/Curses specifies a limit:
Implementations may limit the number of non-spacing characters that can be
associated with a spacing character, provided any limit is at least 5.
The Unix implementations at the time follow that limit:
|
»
|
AIX 4 and OSF1 4 use the same declaration with an array of 5 non-spacing
characters z and a single spacing character c.
|
|
»
|
HP-UX 10 uses an opaque structure with 28 bytes,
which is large enough for the 6 wchar_t values.
|
|
»
|
Solaris xpg4 curses uses a single array of 6 wchar_t values.
|
This implementation's
cchar_t was defined in 1995
using
5 for the total of spacing and non-spacing characters
(
CCHARW_MAX).
That was probably due to a misreading of the AIX 4 header files,
because the X/Open Curses document was not generally available at that time.
Later (in 2002), this detail was overlooked when beginning to implement
the functions using the structure.
In practice, even four non-spacing characters may seem enough.
X/Open Curses documents possible uses for non-spacing characters,
including using them for ligatures between characters
(a feature apparently not supported by any curses implementation).
Unicode does not limit the (analogous) number of combining characters,
so some applications may be affected.