[Xcb] [PATCH proto 16/18] Enforce a bit or value in enum items

Daniel Martin consume.noise at gmail.com
Sun Aug 18 07:54:16 PDT 2013


Do not allow enum items without an explicit bit or value. The value of
an enum item is known when adding the enum to the xml specification.
There's no reason why this information shouldn't be where it belongs to.

Signed-off-by: Daniel Martin <consume.noise at gmail.com>
---
 src/xcb.xsd | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/xcb.xsd b/src/xcb.xsd
index 819495b..7a9c800 100644
--- a/src/xcb.xsd
+++ b/src/xcb.xsd
@@ -353,7 +353,10 @@ authorization from the authors.
           <xsd:sequence minOccurs="1" maxOccurs="unbounded">
             <xsd:element name="item">
               <xsd:complexType>
-                <xsd:group ref="expression" minOccurs="0" maxOccurs="1" />
+                <xsd:choice minOccurs="1" maxOccurs="1">
+                  <xsd:element name="value" type="dec-or-hex-integer" />
+                  <xsd:element name="bit" type="xsd:integer" />
+                </xsd:choice>
                 <xsd:attribute name="name" type="xsd:string" use="required" />
               </xsd:complexType>
             </xsd:element>
-- 
1.8.3.3



More information about the Xcb mailing list