From 1d128f884eaf397738fd36497d09b349ff842ebc Mon Sep 17 00:00:00 2001
From: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Date: Fri, 20 Jul 2018 19:09:13 -0400
Subject: [PATCH 4/6] Use correct types to parse NumPy array dimensions.

The wrong type can cause errors on big-endian systems or others with
differing int and pointer sizes.

Signed-off-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
---
 pyfastnoisesimd/wrapper.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pyfastnoisesimd/wrapper.cpp b/pyfastnoisesimd/wrapper.cpp
index 019ef55..4ebcee8 100644
--- a/pyfastnoisesimd/wrapper.cpp
+++ b/pyfastnoisesimd/wrapper.cpp
@@ -93,7 +93,7 @@ PyFNS_GetEmptySet(PyObject *self, PyObject *args)
 {
     // Make a NumPy array and return it. Note the array is empty, not zeroed.
     npy_intp dims[3] = {0, 0, 0};
-    const char *format = "i|ii";
+    const char *format = "n|nn";
     float *data;
 
     if (!PyArg_ParseTuple(args, format, &dims[0], &dims[1], &dims[2])) {
@@ -538,7 +538,7 @@ PyFNS_GetNoiseSet(FNSObject *self, PyObject *args)
     int xStart, yStart, zStart;
     npy_intp dims[3] = {0, 0, 0};
     float scaleMod = 1.0;
-    const char *format = "iiiiii|f";
+    const char *format = "iiinnn|f";
     float *data = NULL;
 
     if (!PyArg_ParseTuple(args, format, &zStart, &yStart, &xStart, &dims[0], &dims[1], &dims[2], &scaleMod))
-- 
2.17.1