[Xcb] [PATCH proto 1/1] remove valueparam from the xml-xcb documentation

Christian Linhart chris at demorecorder.com
Sun Feb 22 01:55:07 PST 2015


Reason: Valueparam has been made obsolete by the patches of Jaya Tiwari.

Signed-off-by: Christian Linhart <chris at demorecorder.com>
---
 doc/xml-xcb.txt | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/doc/xml-xcb.txt b/doc/xml-xcb.txt
index f8129ea..8fb9b75 100644
--- a/doc/xml-xcb.txt
+++ b/doc/xml-xcb.txt
@@ -229,24 +229,14 @@ enum; the value is restricted to one of the constants named in the enum.
 
   This element represents a field in a request that is calculated rather than
   supplied by the caller.  The type attribute declares the data type of the
   field, and the name attribute gives the name of the field.  The content is
   the expression giving the value of the field.  See the section "Expressions"
   for details on the expression representation.
 
-<valueparam value-mask-type="identifier" value-mask-name="identifier"
-            value-list-name="identifier" />
-
-  This element represents a BITMASK/LISTofVALUE parameter pair: a bitmask
-  defining the set of values included, and a list containing these values.
-  value-mask-type gives the type of the bitmask; this must be CARD16 or
-  CARD32.  value-mask-name gives the field name of the bitmask, and
-  value-list-name gives the field name of the list of values. Please use
-  <switch> instead for new protocol definitions.
-
 <switch name="identifier"> switch expression
     <bitcase> bitcase expression(s), fields </bitcase>
     <case> case expression(s), fields </case>
 </switch>
 
   This element represents conditional inclusion of fields. It can be viewed
   as sequence of multiple ifs:
@@ -271,16 +261,15 @@ enum; the value is restricted to one of the constants named in the enum.
   A switch may contain multiple <bitcase> or <case> elements.
   Usually it will only contain <bitcase> elements
   or only contain <case> elements.
   That is, mixing of <case> and <bitcase> usually doesn't make any sense.
 
   The same value may appear in multiple <case> or <bitcase> elements.
 
-  New protocol definitions should prefer to use this instead of <valueparam>
-  and instead of <union>.
+  New protocol definitions should prefer to use this instead of <union>.
 
 
 Expressions
 -----------
 
   Expressions consist of a tree of <op> elements with leaves consisting of
   <fieldref> or <value> elements.
-- 
2.0.1



More information about the Xcb mailing list