This fixes issue #31 by documenting a couple of fields of IntegerType.
The bug is just that min_value and max_value are not documented.
I looked and all the other fields are documented.
It would be nice if there were a way to verify that each field or method
is also documented, so that "make" would fail if something were missing.
Offhand I am not sure how best to do this.
Tom
From 51de57a5b9ddb150d5eceee9332538caca87c7b1 Mon Sep 17 00:00:00 2001
From: Tom Tromey <tromey(a)redhat.com>
Date: Tue, 24 Jan 2012 13:49:36 -0700
Subject: [PATCH 2/2] Fix issue #31
---
docs/tree.rst | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/docs/tree.rst b/docs/tree.rst
index cd3090f..d3798ad 100644
--- a/docs/tree.rst
+++ b/docs/tree.rst
@@ -425,6 +425,14 @@ Types
The gcc.IntegerType for the unsigned version of this type
+ .. py:attribute:: max_value
+
+ The maximum possible value for this type, as a `gcc.IntegerCst`
+
+ .. py:attribute:: min_value
+
+ The minimum possible value for this type, as a `gcc.IntegerCst`
+
.. py:class:: gcc.FloatType
Subclass of :py:class:`gcc.Type` representing C's `float` and `double` types
--
1.7.6.5