[PYTHON MATRIX-SIG] type coercion one more time

Hinsen Konrad hinsenk@ere.umontreal.ca
Thu, 25 Jan 1996 12:15:06 -0500

     Also, I don't recall anyone presenting a list of 'nice' names for
   the Matrix functions as Konrad has been advocating. I think having
   these is a good idea; the type code that we have now has always seemed
   somehow counter to (my view of) the Python 'do-it-the-Right-Way'
   attitude.  If I actually list them all out here, maybe this will force
   the issue and start some discussion. Comments on the following?

      Array_Char, Array_UChar
      Array_Short, Array_UShort
      Array_Float, Array_Double,
      Array_FloatComplex, Array_DoubleComplex

   'Unsigned' instead of 'U'? XArray instead of Array_X? BTW, is the C

Do we have unsigned types? I proposed a similar list of names a
while ago, using "XArray" instead of "Array_X". I prefer that form
because it is closer to the real-life expressions "integer array",
"float array" etc. But the main point is to get rid of these
silly type codes!

Konrad Hinsen                     | E-Mail: hinsenk@ere.umontreal.ca
Departement de chimie             | Tel.: +1-514-343-6111 ext. 3953
Universite de Montreal            | Fax:  +1-514-343-7586
C.P. 6128, succ. Centre-Ville     | Deutsch/Esperanto/English/Nederlands/
Montreal (QC) H3C 3J7             | Francais (phase experimentale)

MATRIX-SIG  - SIG on Matrix Math for Python

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