Discussion: new operators for numerical computation

Robin Becker robin at jessikat.fsnet.co.uk
Thu Jul 20 03:38:35 EDT 2000


In article <m2u2dl1xf4.fsf at spiff.home.com>, Tim Hochberg
<tim.hochberg at ieee.org> writes
>Huaiyu Zhu <huaiyu_zhu at yahoo.com> writes:
>Based on my ramblings I'll toss out a proposed operator set for the
>pack to feed upon:

>
>       Operator        Name
>          .*             matmul
>          ./             matdiv
>          /.             matsol
>          .** or(?) .^   matpow
>         *              mul
>         /              div
>         %,^,&,|,**     mod, xor, and, or, pow
>
>With broadcasting / nonbroadcasting decided by the individual packages.
>
>My 3 cents.
>
>-tim


The real trichotomy is between inner, outer and element type operations
(I leave out Kronecker products which many use). 

Using . to start an operator seems in Python to lead to all sorts of
confusion

A=Matrix()....; B=A.*C
A=F().........; B=A.*C

No way for the parser to know if the latter should be A.f*C
-- 
Robin Becker



More information about the Python-list mailing list