Re: How to understand this
From: Rui Tang (tangrui76_nospam_at_hotmail.com)
Date: 12/15/04
- Next message: Paul G. Tobey [eMVP]: "Re: hai Bytekeeper & Paul G Tobey"
- Previous message: Dale Ziebarth: "Re: hai Bytekeeper & Paul G Tobey"
- In reply to: Ulrich Eckhardt: "Re: How to understand this"
- Next in thread: Zhongwei Wang at AppliedData Dot Net: "Re: How to understand this"
- Reply: Zhongwei Wang at AppliedData Dot Net: "Re: How to understand this"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Dec 2004 09:57:10 -0800
Are you suggesting that makes the following?
MEMBLOCK *NKSection[BLOCK_MASK+1];
"Ulrich Eckhardt" <doomster@knuut.de> wrote in message
news:32achmF3hvvh5U2@individual.net...
> Rui Tang wrote:
>> typedef MEMBLOCK *SECTION[BLOCK_MASK+1];
>>
>> A little bit confused with the usage of the last typedef. If a variable
>> is then declared as SECTION, like the following statement:
>>
>> SECTION NKSection;
>>
>> how will NKSection look like in memory?
>>
>> Can anyone help to translate this in a more understandable way? Thanks
>> in advance.
>
> You have to read typedefs from the inside out (reading from left to right
> only applies when typedefing objecttypes, not for functions or arrays),
> starting at the newly introduced name. In this case, SECTION is an array
> of
> (BLOCK_MASK+1) pointers to MEMBLOCK.
>
> Uli
>
- Next message: Paul G. Tobey [eMVP]: "Re: hai Bytekeeper & Paul G Tobey"
- Previous message: Dale Ziebarth: "Re: hai Bytekeeper & Paul G Tobey"
- In reply to: Ulrich Eckhardt: "Re: How to understand this"
- Next in thread: Zhongwei Wang at AppliedData Dot Net: "Re: How to understand this"
- Reply: Zhongwei Wang at AppliedData Dot Net: "Re: How to understand this"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|