On Fri, Feb 22, 2013 at 07:17:52AM +0100, Igor Mammedov wrote: [...] > > > > Or, maybe we shouldn't even add a "kvmclock" property at all, and > > translate the legacy "kvmclock" flag to kvmclock1|kvmclock2 inside > > parse_featurestr()? > That's what I was proposing a while back. Lets do it this way.
Probably that was at the time when I still wanted to put all compatibility code inside property getters/setters, but now we are going to keep most compatibility code inside parse_featurestr(). Also, at that time I wasn't aware how annoying and complicated it was to define custom setters/getters for static DeviceClass properties. -- Eduardo
