Re: [PATCH v2 00/16] arm: A9MPCore+A15MPCore QOM'ification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 23.07.2013 23:55, schrieb Alexander Graf:
> On 23.07.2013, at 23:52, Peter Maydell wrote:
>> On 23 July 2013 22:36, Alexander Graf <agraf@xxxxxxx> wrote:
>>>
>>> Or maybe
>>>
>>> struct MyObject {
>>>  PUBLIC_FIELDS
>>>  __field int publicfield;
>>>  PRIVATE_FIELDS
>>>  __field int privatefield;
>>> }
>>
>> I can't see an obvious way to make those do the right
>> thing with the C preprocessor... am I missing something?
> 
> No, I'm probably just daydreaming :). Macros can't redefine other defines, so this probably won't work....
> 
> So yes, prepending the visibility on every field seems to be the most straight forward choice.

I wonder how many public fields do we actually have? Close to zero?
Might there be a way to mark all fields of a struct as private at struct
level, except for those explicitly marked up as public?

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm





[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux