From: <kon...@la...> - 2005-03-04 13:37:16
|
On Mar 3, 2005, at 17:46, Colin J. Williams wrote: >> Those are just the built-in types. There are no plans to increase=20 >> their number. > > My understanding was that there was to be a new builtin=20 > multiarray/Array class/type which eventually would replace the=20 > existing array.ArrayType. Thus, for a time Neither the current array type nor the proposed multiarray type are=20 builtin types. They are types defined in modules belonging to the=20 standard library. > Yes, that it a problem which is not well resolved by requiring that a=20= > slice be terminated with a ")", "]", "}" or a space. One of the=20 > difficulties is that the slice is not recognized in the current=20 > syntax. We have a "slicing" which ties a slice with a It is, but in the form of a standard constructor: slice(a, b, c). > Thomas Wouters proposed a similar structure for a range in PEP204=20 > (http://python.fyxm.net/peps/pep-0204.html), which was rejected. > We would probably face the same problem: a syntax change must matter to=20= many people to have a chance of being accepted. Konrad. -- --------------------------------------------------------------------- Konrad Hinsen Laboratoire L=E9on Brillouin, CEA Saclay, 91191 Gif-sur-Yvette Cedex, France Tel.: +33-1 69 08 79 25 Fax: +33-1 69 08 82 61 E-Mail: kh...@ce... --------------------------------------------------------------------- |