Russell E. Owen wrote: >In article <[EMAIL PROTECTED]>, > Travis Oliphant <[EMAIL PROTECTED]> wrote: > > > >>3) C-API names have prefix PyArray_ (like always), NPY_ or npy_. >> >> The NPY_ and npy_ prefixes are new and were done to remove the >> likelihood of name collisions when NumPy is used with another >> library. The old (and un-prefixed) names are accessible by >> importing numpy/noprefix.h instead of numpy/arrayobject.h >> >> > >This may be too late or too picky, but... > >This seems like too many choices, leading to possible confusion when >reading other people's extensions or the numpy code itself. Could you >standardize on one (I like npy_) or two (if you have to keep PyArray_ >for some reason and can't put it in a backwards-compatibility header >somewhere). > > > There is a logic behind it though.
The C-API function calls all have PyArray_ prefixes (as always in Numeric) The macro captialized constants have NPY_ prefixes Newly defined types with lower-case names have npy_ prefixes -Travis ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
