[PYTHON MATRIX-SIG] Let's get going

Jim Fulton, U.S. Geological Survey jfulton@usgs.gov
Wed, 13 Sep 1995 14:34:11 -0400

On Wed, 13 Sep 1995 14:28:26 -0400 
Hinsen Konrad said:
>    > Why would it have to be copied whenever it is passed to a function?
>    > It would be sufficient to make a copy whenever the matrix is
>    > changed.
>    This gets back to my earlier comment that slices, as proposed cannot
>    be matrices because they store a reference to the data from which they
>    were created and a bunch of offsets for accessing the orinal data
>    properly.  When passed to math/sci libraries, they'll have to be
>    converted to real matrices so that their data are contiguous.
> I see. "Function" means "function in an external library", not
> "Python function" as I had assumed.

Python functions won't really care whether they get a "true" matrix,
or a sequence of sequences, as they will use []s to access data in
either case.


MATRIX-SIG  - SIG on Matrix Math for Python

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