API and ABI changes: Removed BigArrayType, Fixed hasobject to an integer (and inserted an unused character for alignment) and renamed it to flags. Re-organized the ArrFuncs structure. Moved NPY_DATETIME and friends to their 'correct' place in the type order.

1 files changed, 4 insertions, 3 deletions

diff --git a/doc/source/reference/c-api.types-and-structures.rst b/doc/source/reference/c-api.types-and-structures.rst
index ece7f341b..8fe698c9b 100644
--- a/doc/source/reference/c-api.types-and-structures.rst
+++ b/doc/source/reference/c-api.types-and-structures.rst
@@ -191,7 +191,8 @@ PyArrayDescr_Type
           char kind;
           char type;
           char byteorder;
-          char hasobject;
+          char unused;
+          int flags;
           int type_num;
           int elsize;
           int alignment;
@@ -208,7 +209,7 @@ PyArrayDescr_Type
     should point to a user-defined typeobject. This typeobject can
     either inherit from array scalars or not. If it does not inherit
     from array scalars, then the :cdata:`NPY_USE_GETITEM` and
-    :cdata:`NPY_USE_SETITEM` flags should be set in the ``hasobject`` flag.
+    :cdata:`NPY_USE_SETITEM` flags should be set in the ``flags`` member.
 
 .. cmember:: char PyArray_Descr.kind
 
@@ -229,7 +230,7 @@ PyArrayDescr_Type
     endian), '=' (native), '\|' (irrelevant, ignore). All builtin data-
     types have byteorder '='.
 
-.. cmember:: char PyArray_Descr.hasobject
+.. cmember:: int PyArray_Descr.flags
 
     A data-type bit-flag that determines if the data-type exhibits object-
     array like behavior. Each bit in this member is a flag which are named