A Dimecres 20 Setembre 2006 12:48, Travis Oliphant va escriure: > Making sure you get the correct data-type is why there are NPY_INT32 and > NPY_INT64 enumerated types. You can't code using NPY_LONG and expect > it will give you the same sizes when moving from 32-bit and 64-bit > platforms. That's a problem that has been fixed with the bitwidth > types. I don't understand why you are using the enumerated types at all > in this circumstance.
Ooops. I didn't know that NPY_INT32 and NPY_INT64 were there. I think this solves all my problems. In fact, you were proposing this from the very beginning, but I was confused because I was hoping to find NPY_INT32 and NPY_INT64 in NPY_TYPES enumerated and I didn't find it there. I didn't realized that NPY_INT32 and NPY_INT64 were defined outside NPY_TYPES as platform independent constants. Blame on me. Sorry about any inconveniences and thanks once more for your patience! -- >0,0< Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data "-" ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion