Michael D
> Cc: Felix Poludov ; edk2-
> de...@lists.01.org
> Subject: Re: [edk2] History question about Base.h and
> its alternate parallel name space Should we change
> it?
>
>
>
> > On Jan 22, 2019, at 9:49 AM, Kinney, Michael D
> wrote:
> >
> > And
>> UINT32 Data1;
>> UINT16 Data2;
>> UINT16 Data3;
>> UINT8 Data4[8];
>> } GUID;
>>
>> Becomes:
>>
>> typedef struct {
>> UINT32 Data1;
>> UINT16 Data2;
>> UINT16 Data3;
>> UINT8 Data4[8];
>> }
> -Original Message-
> From: af...@apple.com [mailto:af...@apple.com]
> Sent: Friday, January 18, 2019 9:24 AM
> To: Felix Poludov
> Cc: Kinney, Michael D ;
> edk2-devel@lists.01.org
> Subject: Re: [edk2] History question about Base.h and
> its alternate parallel name space..
x Polyudov; 'Andrew Fish'; Kinney, Michael D
> Cc: edk2-devel@lists.01.org
> Subject: RE: [edk2] History question about Base.h and its alternate parallel
> name space Should we change it?
>
> Felix,
>
> Is there a specific set that would have the most benefit?
&g
ubject: RE: [edk2] History question about Base.h and its alternate parallel
name space.... Should we change it?
Felix,
Is there a specific set that would have the most benefit?
Is EFI_GUID sufficient?
Mike
> -Original Message-
> From: Felix Polyudov [mailto:fel...@ami.com]
&
Cc: edk2-devel@lists.01.org
> Subject: RE: [edk2] History question about Base.h and
> its alternate parallel name space Should we change
> it?
>
> I agree with Andrew.
> In my opinion, moving alias types to Base.h will help to
> overcome certain practical inconveniences withou
Behalf Of Andrew
Fish via edk2-devel
Sent: Wednesday, January 16, 2019 5:18 PM
To: Mike Kinney
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2] History question about Base.h and its alternate parallel
name space Should we change it?
> On Jan 16, 2019, at 1:19 PM, Kinney, Michael D
>
sts.01.org] On Behalf Of Andrew Fish via edk2-
>> devel
>> Sent: Wednesday, January 16, 2019 1:00 PM
>> To: edk2-devel
>> Subject: [edk2] History question about Base.h and its
>> alternate parallel name space Should we change it?
>>
>> I had some one
Sent: Wednesday, January 16, 2019 1:00 PM
> To: edk2-devel
> Subject: [edk2] History question about Base.h and its
> alternate parallel name space Should we change it?
>
> I had some one ask me recently why EFI_GUID does not
> work with #include . I explained they needed
I had some one ask me recently why EFI_GUID does not work with #include
. I explained they needed to use GUID vs. EFI_GUID. That prompted the
question of why we have 2 names for the same thing. Well the historical
answer was kind of political as some team wanted to use edk2, but not implemen
10 matches
Mail list logo
