4 Oct 18:12
Warnings for Travis
From: Charles R Harris <charlesr.harris <at> gmail.com>
Subject: Warnings for Travis
Newsgroups: gmane.comp.python.numeric.general
Date: 2008-10-04 16:16:37 GMT
Subject: Warnings for Travis
Newsgroups: gmane.comp.python.numeric.general
Date: 2008-10-04 16:16:37 GMT
Hi Travis,
The following turned up on the 64-bit windows buildbot. I don't know what triggers them as they don't normally show, but they look legit.
numpy\core\src\ufuncobject.c(1700) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
numpy\core\src\ufuncobject.c(1701) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
numpy\core\src\ufuncobject.c(2422) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
They involve some of the parameters in the loop object. If this object is not exposed I would suggest making them npy_intp. That said, I don't think casting to int is dangerous in this case.
Chuck
The following turned up on the 64-bit windows buildbot. I don't know what triggers them as they don't normally show, but they look legit.
numpy\core\src\ufuncobject.c(1700) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
numpy\core\src\ufuncobject.c(1701) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
numpy\core\src\ufuncobject.c(2422) : warning C4244: '=' : conversion from 'npy_intp' to 'int', possible loss of data
They involve some of the parameters in the loop object. If this object is not exposed I would suggest making them npy_intp. That said, I don't think casting to int is dangerous in this case.
Chuck
_______________________________________________ Numpy-discussion mailing list Numpy-discussion <at> scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
RSS Feed