On Wed, Apr 20, 2016 at 5:52 PM, Jan Beulich <jbeul...@suse.com> wrote: >>If it's the case that the only code that uses this is in XenServer, >>then I'd say the answer to #1 can be simply, "Don't compile" and >>"Don't do that" respectively; and the answer to #2 can be either >>"Leave it be" or "Remove the enum from the public interface". >> >>If there are other projects that have started to use this interface, >>then we need a better answer to #1 than "Compile but fail in >>unpredicatble ways". > > How would we know whether there are other users?
Well we'd wait for them to complain... at which point we would have had a release with an *incompatible* ABI and no way to change it. So yes, upon consideration, burning the enum value is really the only option. :-) -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
