[MATRIX-SIG] reverse of take?

[Aaron Watters]

> On the other hand, a pointer-based system has clear speed advantages
> if the subarray is accessed more often than it is created.

Yes, I imagine a system where a button object, say, is given a matrix
into which to write its representation when it it told to draw itself.
In the ideal case writes into this matrix should propagate all the
way back to the frame buffer.  For rectangular buttons, as I understand it,
Numeric slices will do this (or something close) now.  For other shapes
it wouldn't.  A heck maybe rects are good enough for that.

Also, (changing my mind here) for, say, fonts it would be nice
to share an array of indices rather than making a new pointer
array for each character.  I think you've convinced me that
sequences of indices are the *right* way, Konrad.  -- Aaron Watters


_______________
MATRIX-SIG  - SIG on Matrix Math for Python

send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org
_______________