A typedef-name denotes a type, and not a sequence of tokens (as does a macro). In your case, LPVOID
denotes the type also denoted by the token sequence void *
. So the diagram looks like
// [...] is the type entity, which we cannot express directly.
LPVOID => [void *]
Semantically if you specify the type const LPVOID
, you get the following diagram (the brackets around the specifiers mean "the type denoted by the specifier"):
// equivalent (think of "const [int]" and "[int] const"):
const LPVOID <=> LPVOID const => const [void *] <=> [void *] const
=> ["const qualified void-pointer"]
It's not the same thing as the token sequence const void *
- because this one would not denote a const qualified pointer type, but rather a pointer to a const qualified type (the thing pointed to would be const).
Syntactically a parameter declaration has the following (simplified) form:
declaration-specifiers declarator
The declaration-specifiers in case of const void *p
are const void
- so the base-type of *p
is a const qualified void
, but the pointer itself is not qualified. In case of const LPVOID p
however the declaration-specifiers specify a const qualified LPVOID
- which means the pointer type itself is qualified, making the parameter declaration identical to void *const p
.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…