I keep running into issues with making struct buffer access work :-) As the temps part of result_code is not moved to generation yet (and that is a change that perhaps cannot happen very quickly), I get problems with CloneNode, even if my node is NOT a temp (as it makes it a temp).
I've tried to wrap my head around InPlaceAssignmentNode for over an hour now without making any headway, so I'm prone to instead splitting it into CInPlaceAssignmentNode and PyInPlaceAssignmentNode in a transform. This should get rid of the need for CloneNodes in the C version and sidestep the issue. What do you think? However I am slightly worried: If the result of a buffer lookup cannot be put in a CloneNode, will other things/obscure usecases suddenly start breaking? I.e. *must* CloneNode be fixed before one can make use of result_code being moved to code generation? Robert: This applies to your recent changes too. "isinstance(x, y) += 2" is not legal, but are there other situations in which an isinstance could be put in a CloneNode? If so we have a bug already. Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
