Signed-off-by: Auke Booij
---
doc/publican/protocol-to-docbook.xsl | 9 +
1 file changed, 9 insertions(+)
diff --git a/doc/publican/protocol-to-docbook.xsl
b/doc/publican/protocol-to-docbook.xsl
index 7b45969..fad207a 100644
--- a/doc/publican/protocol-to-docbook.xsl
+++ b/doc/publican/
Signed-off-by: Auke Booij
---
protocol/wayland.xml | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 59819e9..9c22d45 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -367,7 +
The scanner now checks whether arguments that have an associated
have the right type.
An argument with an enum attribute must be of type int or uint,
and if the with that name has the bitfield attribute
set to true, then the argument must be of type uint.
Signed-off-by: Auke Booij
---
src/scan
There has been plenty of discussion regarding the introduction of new XML
attributes. This series of patches improves on my earlier attempt to find
common ground in this.
Major exclusions from these patches are:
- Support for cross-interface enum referencing (e.g.
wl_shm_pool::create_buffer::
Introduce the enum and bitfield attributes, which allow you to refer to the enum
you are expecting in an argument, and specify which enums are to be thought of
as bitfields.
Signed-off-by: Auke Booij
---
doc/publican/sources/Protocol.xml | 41 +--
1 file chang
I'm struggling to understand the motivation for this patch.
krh has always said that you need to think of uint and int as two
entirely separate types -- mixing both in math will likely screw up.
You can see this in other places -- widths are often expressed as
signed ints in the protocol, not unsi