[NumPy-Tickets] [NumPy] #1982: In-place arithmetic operations: wrong calculation order?

[NumPy Trac]

#1982: In-place arithmetic operations: wrong calculation order?
------------------------+---------------------------------------------------
 Reporter:  ling        |       Owner:  somebody   
     Type:  defect      |      Status:  new        
 Priority:  normal      |   Milestone:  Unscheduled
Component:  numpy.core  |     Version:  1.6.0      
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by charris):

 I believe gcc got similar complaints when an Intel patch reversed the
 order of memcpy for (putative) efficiency reasons. It broke the Adobe
 flash plugin among other things.

 In place operations are always going to be tricky, what with views and
 all, and it isn't clear that the intended order can always be deduced. A
 warning message might be useful though.

-- 
Ticket URL: <http://projects.scipy.org/numpy/ticket/1982#comment:3>
NumPy <http://projects.scipy.org/numpy>
My example project