[Numpy-discussion] Ill-defined in-place operations (#1085)

Matthieu Brucher matthieu.brucher@gmail....
Wed Apr 15 15:43:56 CDT 2009

2009/4/15  <josef.pktd@gmail.com>:
> On Wed, Apr 15, 2009 at 4:34 PM, Matthieu Brucher
> <matthieu.brucher@gmail.com> wrote:
>> I think this is unavoidable. If we state clearly that every numpy
>> function assums non-pointer aliasing, then people have to care about
>> this themselves (like they would in Fortran, or in C++ for object-like
>> arrays).
> "non-pointer aliasing"
> this might be clear for those that come from fortran or c++.
> But for those that come from matlab or gauss, the intuition is  "what
> you see is what you get", and I have no idea what "non-pointer
> aliasing" is.

It happens when an output pointer is also used as an input (with a
potential offset). And even Fortran, C or C++ programmers don't know
what it is :|

Information System Engineer, Ph.D.
Website: http://matthieu-brucher.developpez.com/
Blogs: http://matt.eifelle.com and http://blog.developpez.com/?blog=92
LinkedIn: http://www.linkedin.com/in/matthieubrucher

More information about the Numpy-discussion mailing list