> I think that totally depends on how the interface is specified. This > applies only to one of the two ways an <enum> can grow.
What other way can it grow? It can only grow bigger. If the application isn't aware of new values added, it should output a warning or an error. On Fri, 24 Apr 2015 22:05 Bill Spitzak <spit...@gmail.com> wrote: > Since all the codegen packages that want to use this enum attribute have > not been written yet I don't think back-compatibility is an issue. They > are not using uint because they do not exist yet! > > The C codegen can continue to ignore the enum, or use it in a way that > does not break code that tries to pass an integer or the wrong enum. > > On 04/24/2015 12:07 AM, Pekka Paalanen wrote: > > > The purpose of docenum was purely for documentation. An API generator > > must ignore all docenum annotations. This was the backward-compatible > > addition. > > > > Any attribute that modifies the generated API in incompatible ways > > cannot be added after the interface has been released as stable. If > > your function argument was uint, and you change it to an enum in a > > strictly typed language, does it not have a good chance of breaking > > someone's build? >
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
