A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-July/006317.html below:

Introducing new operators for matrix computation]

[Python-Dev] [Fwd: Discussion: Introducing new operators for matrix computation] [Python-Dev] [Fwd: Discussion: Introducing new operators for matrix computation]Andrew Kuchling akuchlin@mems-exchange.org
Wed, 12 Jul 2000 20:13:44 -0400
On Wed, Jul 12, 2000 at 05:52:56PM -0500, Paul Prescod quoted:
>From: hzhu@knowledgetrack.com (Huaiyu Zhu)
>The implementors of both previous patches have cautioned that Guido is
>unlikely to adopt the patch for the .* or @* operators.  But I'm quite
>confident that he can be persuaded.  There is a large number of users of

Why not simply write a new parser for this application that generates
the desired semantics?  Maintaining a complete fork of the Python
source might not be necessary if Jeremy's Python parsing/compiling
framework could be easily modified to implement the new operators.

(While a Python variant isn't something I'm enthused about, one
language can't be all things to all people, and I don't see why matrix
operations are so important as to get extra specialized operators;
lots of people use Python for text processing or for COM, so why
shouldn't special syntax be added for *those* applications?  Having a
special parser also means that other matrix-specific language changes
could be made.)

--amk



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4